securityHTML

The sandbox="" attribute should always be added to iframes with untrusted or third-party sources. The attribute enables different types of iframe content restrictions like script or form execution.

• <iframe allowfullscreen="" frameborder="0" height="375" src="https://www.youtube.com/embed/lzO4xPmWKmw" width="660"></iframe>[http://www.stmartincentre.org.za/]
• <iframe allowfullscreen="" frameborder="0" height="450" src="https://www.google.com/maps/embed?pb=!1m14!1m8!1m3!1d28624.301555517504!2d28.43302!3d-26.26044!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x1e95244ebd5e4691%3A0x265486dcc65c5a79!2s46+Derby+Ave%2C+Springs%2C+1560%2C+South+Africa!5e0!3m2!1sen!2sus!4v1472182015902" style="border:0" width="600"></iframe>[http://www.stmartincentre.org.za/]
• <iframe allowfullscreen="" class="giphy-embed" frameborder="0" height="300" src="//giphy.com/embed/11S1Zy5SPIqv84" width="220"></iframe>[http://www.stmartincentre.org.za/]

If a resource is loaded over src="http://...", it may not be transmitted over the TLS protocol. In case the webpage is loaded over HTTPS, this results in a mixed content situation where the page is securely loaded but has unencrypted resources embedded. This will often lead to a mixed-content browser warning, but at the time this is reported, it is most likely to late and the attack could have already succeeded.

• <script async="async" src="http://www.stmartincentre.org.za/media/com_acymailing/js/acymailing_module.js?v=5104" type="text/javascript"></script>[http://www.stmartincentre.org.za/]
• <link href="http://www.stmartincentre.org.za/media/com_acymailing/css/module_default.css?v=1536980253" rel="stylesheet" type="text/css"></link>[http://www.stmartincentre.org.za/]
• <img border="0" height="250" src="http://www.ibreviary.org/images/banners/ibreviaryweb_en.png" width="300"></img>[http://www.stmartincentre.org.za/]

The crossorigin="anonymous" attribute should always be added to external ressources so no user credentials are transmitted. By loading external files with a GET request, http user credentials are exchanged by default. If the source host is corrupted, an attacker could these details for attacks.

• <img border="0" height="250" src="http://www.ibreviary.org/images/banners/ibreviaryweb_en.png" width="300"></img>[http://www.stmartincentre.org.za/]

The integrity="sha256-..." attribute should always be added to external file hosted on another domain, because an unexpected manipulation / corruption of the code can lead to session hijacking or similar script releated attacks.

• <img border="0" height="250" src="http://www.ibreviary.org/images/banners/ibreviaryweb_en.png" width="300"></img>[http://www.stmartincentre.org.za/]

The rel="noreferrer" attribute should always be added to external links to prevent reverse tabnabbing for older browser, which do not support the rel="noopener" attribute and to prevent phishing attacks.

• <a href="http://www.zaop.org/" rel="noopener" target="_blank"><img alt="dominicanseal" height="200" src="/images/stories/dominicanseal.jpg" style="display: block; margin-left: auto; margin-right: auto;" width="200"></img></a>[http://www.stmartincentre.org.za/]
• <a href="http://giphy.com/gifs/trippy-dope-11S1Zy5SPIqv84"></a>[http://www.stmartincentre.org.za/]
• <a href="http://sacatholiconline.org/"><img alt="sacatholic ad" height="442" src="/images/stories/sacatholic_ad.jpg" style="display: block; margin-left: auto; margin-right: auto;" width="200"></img></a>[http://www.stmartincentre.org.za/]
• <a href="http://www.radioveritas.co.za" target="_blank"><img alt="veritas" height="155" src="/images/stories/veritas.png" style="display: block; margin: 5px auto;" width="180"></img></a>[http://www.stmartincentre.org.za/]
• <a href="http://www.sacatholiconline.org/" rel="noopener" style="color: #0000ff;" target="_blank">SA Catholic Online - for all your website and publishing needs!</a>[http://www.stmartincentre.org.za/]
• <a href="http://www.joomlashine.com" target="_blank" title="Free Hi-Quality Joomla Templates on JoomlaShine">JoomlaShine.com</a>[http://www.stmartincentre.org.za/]

The rel="noopener" attribute should always be added to external links, which open in a new tab, to reduce the risk of reverse tabnabbing. Otherwise javascript on the new page has full control over the previous visited page, including permission to change the DOM object and possibly steal session cookies.

• <a href="http://www.radioveritas.co.za" target="_blank"><img alt="veritas" height="155" src="/images/stories/veritas.png" style="display: block; margin: 5px auto;" width="180"></img></a>[http://www.stmartincentre.org.za/]
• <a href="http://www.joomlashine.com" target="_blank" title="Free Hi-Quality Joomla Templates on JoomlaShine">JoomlaShine.com</a>[http://www.stmartincentre.org.za/]

The <meta name="generator" content="WordPress x.x"></meta> and the <meta content="deny" http-equiv="X-Frame-Options"></meta> meta-tags should always be removed from the html body since the generator tag provides critical informations about the used CMS and the X-Frame-Options must be specified as HTTP Headers and not as a meta tag. Most browser will ignore the meta tag, which can lead to unintended misbehaviour.

• <meta content="Joomla! - Open Source Content Management" name="generator"></meta>[http://www.stmartincentre.org.za/]

The sandbox="" attribute should always be added to iframes with untrusted or third-party sources. The attribute enables different types of iframe content restrictions like script or form execution.

The crossorigin="anonymous" attribute should always be added to external ressources so no user credentials are transmitted. By loading external files with a GET request, http user credentials are exchanged by default. If the source host is corrupted, an attacker could these details for attacks.

The integrity="sha256-..." attribute should always be added to external file hosted on another domain, because an unexpected manipulation / corruption of the code can lead to session hijacking or similar script releated attacks.

The rel="noopener" attribute should always be added to external links, which open in a new tab, to reduce the risk of reverse tabnabbing. Otherwise javascript on the new page has full control over the previous visited page, including permission to change the DOM object and possibly steal session cookies.

The rel="noreferrer" attribute should always be added to external links to prevent reverse tabnabbing for older browser, which do not support the rel="noopener" attribute and to prevent phishing attacks.

If a resource is loaded over src="http://...", it may not be transmitted over the TLS protocol. In case the webpage is loaded over HTTPS, this results in a mixed content situation where the page is securely loaded but has unencrypted resources embedded. This will often lead to a mixed-content browser warning, but at the time this is reported, it is most likely to late and the attack could have already succeeded.

The pattern="..." attribute should always be added to password fields, since a client-side password strength can not be enforced by JavaScript, if the user has disabled scripts in his browser. Make sure to perform a second check at sever-side.

The <meta name="generator" content="WordPress x.x"></meta> and the <meta content="deny" http-equiv="X-Frame-Options"></meta> meta-tags should always be removed from the html body since the generator tag provides critical informations about the used CMS and the X-Frame-Options must be specified as HTTP Headers and not as a meta tag. Most browser will ignore the meta tag, which can lead to unintended misbehaviour.

Cross-site request forgery, also known as one-click attack or session riding, is a type of malicious exploit of a website where unauthorized commands are transmitted from a authenticated user on the web application. One way of performing such an attack is to observe the HTML code of a website for session tokens like in <input> tags, which should never be stored inside of the HTML-document.

If the debugging is enabled on a production server, it may give an agressor valuable informations about the inner structure of a web application. These can be used to find vulnerabilities for injections or other type of attacks. Therefore, debugging should always be disabled.