<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OWASP_2025_A05 on ZAP</title>
    <link>/alerttags/owasp_2025_a05/</link>
    <description>Recent content in OWASP_2025_A05 on ZAP</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/alerttags/owasp_2025_a05/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Advanced SQL Injection</title>
      <link>/docs/alerts/90018/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90018/</guid>
      <description>&lt;p&gt;A SQL injection may be possible using the attached payload.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AngularJS $parse expression from cookie</title>
      <link>/docs/alerts/210009-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210009-3/</guid>
      <description>&lt;p&gt;Cookie-controlled expression value reaches AngularJS $parse.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>AngularJS $parse expression from form input</title>
      <link>/docs/alerts/210009-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210009-2/</guid>
      <description>&lt;p&gt;Form-controlled expression value reaches AngularJS $parse.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>AngularJS $parse expression from localStorage</title>
      <link>/docs/alerts/210009-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210009-4/</guid>
      <description>&lt;p&gt;Storage-controlled expression value reaches AngularJS $parse.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>AngularJS $parse expression from postMessage</title>
      <link>/docs/alerts/210009-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210009-5/</guid>
      <description>&lt;p&gt;postMessage-controlled expression value reaches AngularJS $parse.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>AngularJS expression executed through Function constructor</title>
      <link>/docs/alerts/210009-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210009-1/</guid>
      <description>&lt;p&gt;Tainted data reached dynamic code execution while AngularJS expression parsing/compilation was active. This covers interpolation and $parse-style AngularJS expression injection cases.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>AngularJS interpolation delimiters in template string</title>
      <link>/docs/alerts/220004-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220004-5/</guid>
      <description>&lt;p&gt;Finds AngularJS code patterns where untrusted data is compiled or parsed as AngularJS expressions/templates, including $parse, $interpolate, $compile, interpolation delimiters and ng-* expression attributes.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>AngularJS ng-* expression attribute</title>
      <link>/docs/alerts/220004-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220004-6/</guid>
      <description>&lt;p&gt;Finds AngularJS code patterns where untrusted data is compiled or parsed as AngularJS expressions/templates, including $parse, $interpolate, $compile, interpolation delimiters and ng-* expression attributes.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Avoid eval with string literals</title>
      <link>/docs/alerts/220003-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220003-3/</guid>
      <description>&lt;p&gt;Detects dynamic execution of attacker-controlled strings in JavaScript sinks such as eval(), Function(), string-based timers, execScript, or script.text assignments. Exploiting these flows lets attackers execute arbitrary JS without relying on HTML injection.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Avoid execScript dynamic execution</title>
      <link>/docs/alerts/220003-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220003-2/</guid>
      <description>&lt;p&gt;Detects dynamic execution of attacker-controlled strings in JavaScript sinks such as eval(), Function(), string-based timers, execScript, or script.text assignments. Exploiting these flows lets attackers execute arbitrary JS without relying on HTML injection.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Avoid Function constructor with strings</title>
      <link>/docs/alerts/220003-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220003-4/</guid>
      <description>&lt;p&gt;Detects dynamic execution of attacker-controlled strings in JavaScript sinks such as eval(), Function(), string-based timers, execScript, or script.text assignments. Exploiting these flows lets attackers execute arbitrary JS without relying on HTML injection.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Avoid string-based timers</title>
      <link>/docs/alerts/220003-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220003-1/</guid>
      <description>&lt;p&gt;Detects dynamic execution of attacker-controlled strings in JavaScript sinks such as eval(), Function(), string-based timers, execScript, or script.text assignments. Exploiting these flows lets attackers execute arbitrary JS without relying on HTML injection.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Buffer Overflow</title>
      <link>/docs/alerts/30001/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/30001/</guid>
      <description>&lt;p&gt;Buffer overflow errors are characterized by the overwriting of memory spaces of the background web process, which should have never been modified intentionally or unintentionally. Overwriting values of the IP (Instruction Pointer), BP (Base Pointer) and other registers causes exceptions, segmentation faults, and other process errors to occur. Usually these errors end execution of the application in an unexpected way.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cookie Poisoning</title>
      <link>/docs/alerts/10029/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10029/</guid>
      <description>&lt;p&gt;This check looks at user-supplied input in query string parameters and POST data to identify where cookie parameters might be controlled. This is called a cookie poisoning attack, and becomes exploitable when an attacker can manipulate the cookie in various ways. In some cases this will not be exploitable, however, allowing URL parameters to set cookie values is generally considered a bug.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CRLF Injection</title>
      <link>/docs/alerts/40003/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40003/</guid>
      <description>&lt;p&gt;Cookie can be set via CRLF injection. It may also be possible to set arbitrary HTTP response headers. In addition, by carefully crafting the injected response using cross-site script, cache poisoning vulnerability may also exist.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross Site Scripting (DOM Based)</title>
      <link>/docs/alerts/40026/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40026/</guid>
      <description>&lt;p&gt;Cross-site Scripting (XSS) is an attack technique that involves echoing attacker-supplied code into a user&amp;rsquo;s browser instance. A browser instance can be a standard web browser client, or a browser object embedded in a software product such as the browser within WinAmp, an RSS reader, or an email client. The code itself is usually written in HTML/JavaScript, but may also extend to VBScript, ActiveX, Java, Flash, or any other browser-supported technology.&#xA;When an attacker gets a user&amp;rsquo;s browser to execute his/her code, the code will run within the security context (or zone) of the hosting web site. With this level of privilege, the code has the ability to read, modify and transmit any sensitive data accessible by the browser. A Cross-site Scripted user could have his/her account hijacked (cookie theft), their browser redirected to another location, or possibly shown fraudulent content delivered by the web site they are visiting. Cross-site Scripting attacks essentially compromise the trust relationship between a user and the web site. Applications utilizing browser object instances which load content from the file system may execute code under the local machine zone allowing for system compromise.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross Site Scripting (Persistent)</title>
      <link>/docs/alerts/40014-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40014-1/</guid>
      <description>&lt;p&gt;Cross-site Scripting (XSS) is an attack technique that involves echoing attacker-supplied code into a user&amp;rsquo;s browser instance. A browser instance can be a standard web browser client, or a browser object embedded in a software product such as the browser within WinAmp, an RSS reader, or an email client. The code itself is usually written in HTML/JavaScript, but may also extend to VBScript, ActiveX, Java, Flash, or any other browser-supported technology.&#xA;When an attacker gets a user&amp;rsquo;s browser to execute his/her code, the code will run within the security context (or zone) of the hosting web site. With this level of privilege, the code has the ability to read, modify and transmit any sensitive data accessible by the browser. A Cross-site Scripted user could have his/her account hijacked (cookie theft), their browser redirected to another location, or possibly shown fraudulent content delivered by the web site they are visiting. Cross-site Scripting attacks essentially compromise the trust relationship between a user and the web site. Applications utilizing browser object instances which load content from the file system may execute code under the local machine zone allowing for system compromise.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross Site Scripting (Persistent)</title>
      <link>/docs/alerts/40014-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40014-3/</guid>
      <description>&lt;p&gt;Cross-site Scripting (XSS) is an attack technique that involves echoing attacker-supplied code into a user&amp;rsquo;s browser instance. A browser instance can be a standard web browser client, or a browser object embedded in a software product such as the browser within WinAmp, an RSS reader, or an email client. The code itself is usually written in HTML/JavaScript, but may also extend to VBScript, ActiveX, Java, Flash, or any other browser-supported technology.&#xA;When an attacker gets a user&amp;rsquo;s browser to execute his/her code, the code will run within the security context (or zone) of the hosting web site. With this level of privilege, the code has the ability to read, modify and transmit any sensitive data accessible by the browser. A Cross-site Scripted user could have his/her account hijacked (cookie theft), their browser redirected to another location, or possibly shown fraudulent content delivered by the web site they are visiting. Cross-site Scripting attacks essentially compromise the trust relationship between a user and the web site. Applications utilizing browser object instances which load content from the file system may execute code under the local machine zone allowing for system compromise.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross Site Scripting (Persistent) - Prime</title>
      <link>/docs/alerts/40016/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40016/</guid>
      <description></description>
    </item>
    <item>
      <title>Cross Site Scripting (Persistent) - Spider</title>
      <link>/docs/alerts/40017/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40017/</guid>
      <description></description>
    </item>
    <item>
      <title>Cross Site Scripting (Reflected)</title>
      <link>/docs/alerts/40012/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40012/</guid>
      <description>&lt;p&gt;Cross-site Scripting (XSS) is an attack technique that involves echoing attacker-supplied code into a user&amp;rsquo;s browser instance. A browser instance can be a standard web browser client, or a browser object embedded in a software product such as the browser within WinAmp, an RSS reader, or an email client. The code itself is usually written in HTML/JavaScript, but may also extend to VBScript, ActiveX, Java, Flash, or any other browser-supported technology.&#xA;When an attacker gets a user&amp;rsquo;s browser to execute his/her code, the code will run within the security context (or zone) of the hosting web site. With this level of privilege, the code has the ability to read, modify and transmit any sensitive data accessible by the browser. A Cross-site Scripted user could have his/her account hijacked (cookie theft), their browser redirected to another location, or possibly shown fraudulent content delivered by the web site they are visiting. Cross-site Scripting attacks essentially compromise the trust relationship between a user and the web site. Applications utilizing browser object instances which load content from the file system may execute code under the local machine zone allowing for system compromise.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross Site Scripting Weakness (Persistent in JSON Response)</title>
      <link>/docs/alerts/40014-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40014-2/</guid>
      <description>&lt;p&gt;A XSS attack was found in a JSON response, this might leave content consumers vulnerable to attack if they don&amp;rsquo;t appropriately handle the data (response).&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL assigned to form action</title>
      <link>/docs/alerts/210006-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210006-3/</guid>
      <description>&lt;p&gt;Tainted data: URL assigned to form action.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL assigned to formAction</title>
      <link>/docs/alerts/210006-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210006-4/</guid>
      <description>&lt;p&gt;Tainted data: URL assigned to formAction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL assigned to href</title>
      <link>/docs/alerts/210003-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-5/</guid>
      <description>&lt;p&gt;Tainted data: URL assigned to href.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL assigned to iframe.src</title>
      <link>/docs/alerts/210003-15/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-15/</guid>
      <description>&lt;p&gt;Tainted data: URL assigned to iframe.src.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL assigned to script.src</title>
      <link>/docs/alerts/210003-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-4/</guid>
      <description>&lt;p&gt;Tainted data: URL assigned to script.src and treated as executable content.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL assigned to src</title>
      <link>/docs/alerts/210003-7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-7/</guid>
      <description>&lt;p&gt;Tainted data: URL assigned to a generic src attribute.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL navigated via location.assign</title>
      <link>/docs/alerts/210003-10/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-10/</guid>
      <description>&lt;p&gt;Tainted data: URL passed to location.assign.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL navigated via location.href</title>
      <link>/docs/alerts/210003-8/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-8/</guid>
      <description>&lt;p&gt;Tainted data: URL assigned to location.href.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL navigated via location.replace</title>
      <link>/docs/alerts/210003-12/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-12/</guid>
      <description>&lt;p&gt;Tainted data: URL passed to location.replace.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>data: URL opened via window.open</title>
      <link>/docs/alerts/210003-14/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-14/</guid>
      <description>&lt;p&gt;Tainted data: URL passed to window.open.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Disallow document.write()/writeln()</title>
      <link>/docs/alerts/220000-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220000-3/</guid>
      <description>&lt;p&gt;Detects cases where untrusted data from the DOM (URL, element values, storage, messages, etc.) flows into HTML/JS execution sinks (e.g., innerHTML, outerHTML, document.write, string-based setTimeout, insertAdjacentHTML) without proper sanitization or encoding \u2014 enabling DOM-based cross-site scripting.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Disallow innerHTML/outerHTML assignments</title>
      <link>/docs/alerts/220000-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220000-1/</guid>
      <description>&lt;p&gt;Detects cases where untrusted data from the DOM (URL, element values, storage, messages, etc.) flows into HTML/JS execution sinks (e.g., innerHTML, outerHTML, document.write, string-based setTimeout, insertAdjacentHTML) without proper sanitization or encoding \u2014 enabling DOM-based cross-site scripting.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Disallow insertAdjacentHTML()</title>
      <link>/docs/alerts/220000-7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220000-7/</guid>
      <description>&lt;p&gt;Detects cases where untrusted data from the DOM (URL, element values, storage, messages, etc.) flows into HTML/JS execution sinks (e.g., innerHTML, outerHTML, document.write, string-based setTimeout, insertAdjacentHTML) without proper sanitization or encoding \u2014 enabling DOM-based cross-site scripting.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via document.write</title>
      <link>/docs/alerts/210000-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210000-5/</guid>
      <description>&lt;p&gt;Tainted data passed to document.write.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via document.write (secondary sources)</title>
      <link>/docs/alerts/210017-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210017-4/</guid>
      <description>&lt;p&gt;Persisted/reflected client-side values reached document.write.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via DOM mutation (secondary sources)</title>
      <link>/docs/alerts/210017-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210017-6/</guid>
      <description>&lt;p&gt;Persisted/reflected client-side values reached mutation sinks.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via DOM mutations</title>
      <link>/docs/alerts/210000-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210000-6/</guid>
      <description>&lt;p&gt;Tainted data inserted into the DOM via DOM mutation APIs.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via DOMParser.parseFromString</title>
      <link>/docs/alerts/210016-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210016-1/</guid>
      <description>&lt;p&gt;Tainted HTML parsed through DOMParser.parseFromString with an HTML-like MIME type.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via Element.innerHTML</title>
      <link>/docs/alerts/210000-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210000-2/</guid>
      <description>&lt;p&gt;Tainted data assigned to innerHTML (possible DOM XSS).&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via Element.outerHTML</title>
      <link>/docs/alerts/210000-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210000-3/</guid>
      <description>&lt;p&gt;Tainted data assigned to outerHTML (possible DOM XSS).&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via Element.setHTMLUnsafe</title>
      <link>/docs/alerts/210016-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210016-3/</guid>
      <description>&lt;p&gt;Tainted HTML passed to Element.setHTMLUnsafe.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via iframe.srcdoc (secondary sources)</title>
      <link>/docs/alerts/210017-7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210017-7/</guid>
      <description>&lt;p&gt;Persisted/reflected client-side values reached iframe.srcdoc.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via inline event handler</title>
      <link>/docs/alerts/210000-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210000-1/</guid>
      <description>&lt;p&gt;Tainted data flowed into an inline event handler.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via inline handlers (secondary sources)</title>
      <link>/docs/alerts/210017-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210017-5/</guid>
      <description>&lt;p&gt;Persisted/reflected client-side values reached inline event handlers.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via innerHTML (Angular)</title>
      <link>/docs/alerts/220000-9/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220000-9/</guid>
      <description>&lt;p&gt;Detects cases where untrusted data from the DOM (URL, element values, storage, messages, etc.) flows into HTML/JS execution sinks (e.g., innerHTML, outerHTML, document.write, string-based setTimeout, insertAdjacentHTML) without proper sanitization or encoding \u2014 enabling DOM-based cross-site scripting.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via innerHTML (secondary sources)</title>
      <link>/docs/alerts/210017-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210017-1/</guid>
      <description>&lt;p&gt;Persisted/reflected client-side values reached innerHTML.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via insertAdjacentHTML</title>
      <link>/docs/alerts/210000-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210000-4/</guid>
      <description>&lt;p&gt;Tainted HTML passed into insertAdjacentHTML.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via insertAdjacentHTML (secondary sources)</title>
      <link>/docs/alerts/210017-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210017-3/</guid>
      <description>&lt;p&gt;Persisted/reflected client-side values reached insertAdjacentHTML.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via outerHTML (secondary sources)</title>
      <link>/docs/alerts/210017-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210017-2/</guid>
      <description>&lt;p&gt;Persisted/reflected client-side values reached outerHTML.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param attribute breakout</title>
      <link>/docs/alerts/200022-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-2/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param attribute-name event injection</title>
      <link>/docs/alerts/200022-11/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-11/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param double-quoted attribute event breakout</title>
      <link>/docs/alerts/200022-12/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-12/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param double-quoted resource onerror breakout</title>
      <link>/docs/alerts/200022-13/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-13/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param event-handler value</title>
      <link>/docs/alerts/200022-10/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-10/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param HTML image onerror</title>
      <link>/docs/alerts/200022-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-1/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param javascript: URL</title>
      <link>/docs/alerts/200022-17/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-17/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param JS block-comment breakout</title>
      <link>/docs/alerts/200022-8/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-8/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param JS double-quote breakout</title>
      <link>/docs/alerts/200022-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-3/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param JS expression execution</title>
      <link>/docs/alerts/200022-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-6/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param JS regex breakout</title>
      <link>/docs/alerts/200022-7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-7/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param JS single-quote breakout</title>
      <link>/docs/alerts/200022-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-4/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param JS template literal breakout</title>
      <link>/docs/alerts/200022-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-5/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param script-tag breakout</title>
      <link>/docs/alerts/200022-9/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-9/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param single-quoted attribute event breakout</title>
      <link>/docs/alerts/200022-14/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-14/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param style-block breakout</title>
      <link>/docs/alerts/200022-18/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-18/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param SVG tag-name event injection</title>
      <link>/docs/alerts/200022-16/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-16/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via query param unquoted attribute event injection</title>
      <link>/docs/alerts/200022-15/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200022-15/</guid>
      <description>&lt;p&gt;Tests top-level GET query parameters for browser-executed XSS by opening a real browser attack tab and requiring an execution marker after load or safe synthetic interaction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via Range.createContextualFragment</title>
      <link>/docs/alerts/210016-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210016-2/</guid>
      <description>&lt;p&gt;Tainted HTML passed to Range.createContextualFragment.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM XSS via ShadowRoot.setHTMLUnsafe</title>
      <link>/docs/alerts/210016-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210016-4/</guid>
      <description>&lt;p&gt;Tainted HTML passed to ShadowRoot.setHTMLUnsafe.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM-based JavaScript Injection (taint flow)</title>
      <link>/docs/alerts/220003-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220003-5/</guid>
      <description>&lt;p&gt;Detects dynamic execution of attacker-controlled strings in JavaScript sinks such as eval(), Function(), string-based timers, execScript, or script.text assignments. Exploiting these flows lets attackers execute arbitrary JS without relying on HTML injection.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>DOM-based XSS (taint flow)</title>
      <link>/docs/alerts/220000-8/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220000-8/</guid>
      <description>&lt;p&gt;Detects cases where untrusted data from the DOM (URL, element values, storage, messages, etc.) flows into HTML/JS execution sinks (e.g., innerHTML, outerHTML, document.write, string-based setTimeout, insertAdjacentHTML) without proper sanitization or encoding \u2014 enabling DOM-based cross-site scripting.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dynamic AngularJS $compile/$interpolate template</title>
      <link>/docs/alerts/220004-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220004-4/</guid>
      <description>&lt;p&gt;Finds AngularJS code patterns where untrusted data is compiled or parsed as AngularJS expressions/templates, including $parse, $interpolate, $compile, interpolation delimiters and ng-* expression attributes.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dynamic AngularJS $parse expression</title>
      <link>/docs/alerts/220004-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220004-3/</guid>
      <description>&lt;p&gt;Finds AngularJS code patterns where untrusted data is compiled or parsed as AngularJS expressions/templates, including $parse, $interpolate, $compile, interpolation delimiters and ng-* expression attributes.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dynamic code execution via eval</title>
      <link>/docs/alerts/210001-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210001-1/</guid>
      <description>&lt;p&gt;Tainted string executed via eval().&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dynamic code execution via Function constructor</title>
      <link>/docs/alerts/210001-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210001-2/</guid>
      <description>&lt;p&gt;Tainted string executed via Function constructor.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dynamic code execution via Function.apply</title>
      <link>/docs/alerts/210001-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210001-3/</guid>
      <description>&lt;p&gt;Tainted string executed via Function.apply.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dynamic template compilation</title>
      <link>/docs/alerts/220005-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220005-1/</guid>
      <description>&lt;p&gt;Detects dynamic client-side template compilation/rendering where attacker-controlled templates or outputs are injected into the DOM.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>eval() from storage/referrer taint</title>
      <link>/docs/alerts/210018-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210018-1/</guid>
      <description>&lt;p&gt;Storage/referrer taint reached eval().&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Exponential Entity Expansion (Billion Laughs Attack)</title>
      <link>/docs/alerts/40044/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40044/</guid>
      <description>&lt;p&gt;An exponential entity expansion, or &amp;ldquo;billion laughs&amp;rdquo; attack is a type of denial-of-service (DoS) attack. It is aimed at parsers of markup languages like XML or YAML that allow macro expansions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Expression Language Injection</title>
      <link>/docs/alerts/90025/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90025/</guid>
      <description>&lt;p&gt;The software constructs all or part of an expression language (EL) statement in a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed. In certain versions of Spring 3.0.5 and earlier, there was a vulnerability (CVE-2011-2730) in which Expression Language tags would be evaluated twice, which effectively exposed any application to EL injection. However, even for later versions, this weakness is still possible depending on configuration.&lt;/p&gt;</description>
    </item>
    <item>
      <title>External Redirect</title>
      <link>/docs/alerts/20019-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/20019-1/</guid>
      <description>&lt;p&gt;URL redirectors represent common functionality employed by web sites to forward an incoming request to an alternate resource. This can be done for a variety of reasons and is often done to allow resources to be moved within the directory structure and to avoid breaking functionality for users that request the resource at its previous location. URL redirectors may also be used to implement load balancing, leveraging abbreviated URLs or recording outgoing links. It is this last implementation which is often used in phishing attacks as described in the example below. URL redirectors do not necessarily represent a direct security vulnerability but can be abused by attackers trying to social engineer victims into believing that they are navigating to a site other than the true destination.&lt;/p&gt;</description>
    </item>
    <item>
      <title>External Redirect</title>
      <link>/docs/alerts/20019-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/20019-2/</guid>
      <description>&lt;p&gt;URL redirectors represent common functionality employed by web sites to forward an incoming request to an alternate resource. This can be done for a variety of reasons and is often done to allow resources to be moved within the directory structure and to avoid breaking functionality for users that request the resource at its previous location. URL redirectors may also be used to implement load balancing, leveraging abbreviated URLs or recording outgoing links. It is this last implementation which is often used in phishing attacks as described in the example below. URL redirectors do not necessarily represent a direct security vulnerability but can be abused by attackers trying to social engineer victims into believing that they are navigating to a site other than the true destination.&lt;/p&gt;</description>
    </item>
    <item>
      <title>External Redirect</title>
      <link>/docs/alerts/20019-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/20019-3/</guid>
      <description>&lt;p&gt;URL redirectors represent common functionality employed by web sites to forward an incoming request to an alternate resource. This can be done for a variety of reasons and is often done to allow resources to be moved within the directory structure and to avoid breaking functionality for users that request the resource at its previous location. URL redirectors may also be used to implement load balancing, leveraging abbreviated URLs or recording outgoing links. It is this last implementation which is often used in phishing attacks as described in the example below. URL redirectors do not necessarily represent a direct security vulnerability but can be abused by attackers trying to social engineer victims into believing that they are navigating to a site other than the true destination.&lt;/p&gt;</description>
    </item>
    <item>
      <title>External Redirect</title>
      <link>/docs/alerts/20019-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/20019-4/</guid>
      <description>&lt;p&gt;URL redirectors represent common functionality employed by web sites to forward an incoming request to an alternate resource. This can be done for a variety of reasons and is often done to allow resources to be moved within the directory structure and to avoid breaking functionality for users that request the resource at its previous location. URL redirectors may also be used to implement load balancing, leveraging abbreviated URLs or recording outgoing links. It is this last implementation which is often used in phishing attacks as described in the example below. URL redirectors do not necessarily represent a direct security vulnerability but can be abused by attackers trying to social engineer victims into believing that they are navigating to a site other than the true destination.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Format String Error</title>
      <link>/docs/alerts/30002/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/30002/</guid>
      <description>&lt;p&gt;A Format String error occurs when the submitted data of an input string is evaluated as a command by the application.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Function.apply() from storage/referrer taint</title>
      <link>/docs/alerts/210018-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210018-3/</guid>
      <description>&lt;p&gt;Storage/referrer taint reached Function.apply().&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Function() from storage/referrer taint</title>
      <link>/docs/alerts/210018-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210018-2/</guid>
      <description>&lt;p&gt;Storage/referrer taint reached Function constructor.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>HTTP Parameter Pollution</title>
      <link>/docs/alerts/20014/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/20014/</guid>
      <description>&lt;p&gt;HTTP Parameter Pollution (HPP) attacks consist of injecting encoded query string delimiters into other existing parameters. If a web application does not properly sanitize the user input, a malicious user can compromise the logic of the application to perform either client-side or server-side attacks. One consequence of HPP attacks is that the attacker can potentially override existing hard-coded HTTP parameters to modify the behavior of an application, bypass input validation checkpoints, and access and possibly exploit variables that may be out of direct reach.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Inline event handler built from dynamic data</title>
      <link>/docs/alerts/220000-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220000-6/</guid>
      <description>&lt;p&gt;Detects cases where untrusted data from the DOM (URL, element values, storage, messages, etc.) flows into HTML/JS execution sinks (e.g., innerHTML, outerHTML, document.write, string-based setTimeout, insertAdjacentHTML) without proper sanitization or encoding \u2014 enabling DOM-based cross-site scripting.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Integer Overflow Error</title>
      <link>/docs/alerts/30003/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/30003/</guid>
      <description>&lt;p&gt;An integer overflow condition exists when an integer used in a compiled program extends beyond the range limits and has not been properly checked from the input stream.&lt;/p&gt;</description>
    </item>
    <item>
      <title>javascript: URL assigned to form action</title>
      <link>/docs/alerts/210006-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210006-1/</guid>
      <description>&lt;p&gt;Tainted javascript: URL assigned to form action.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>javascript: URL assigned to formAction</title>
      <link>/docs/alerts/210006-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210006-2/</guid>
      <description>&lt;p&gt;Tainted javascript: URL assigned to formAction.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>javascript: URL assigned to href</title>
      <link>/docs/alerts/210003-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-1/</guid>
      <description>&lt;p&gt;Tainted javascript: URL assigned to href and likely to execute in the current browsing context.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>javascript: URL assigned to iframe.src</title>
      <link>/docs/alerts/210003-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-3/</guid>
      <description>&lt;p&gt;Tainted javascript: URL assigned to iframe.src.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>javascript: URL assigned to src</title>
      <link>/docs/alerts/210003-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-6/</guid>
      <description>&lt;p&gt;Tainted javascript: URL assigned to a generic src attribute and interpreted as executable content.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>javascript: URL navigated via location.assign</title>
      <link>/docs/alerts/210003-9/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-9/</guid>
      <description>&lt;p&gt;Tainted javascript: URL passed to location.assign.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>javascript: URL navigated via location.href</title>
      <link>/docs/alerts/210003-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-2/</guid>
      <description>&lt;p&gt;Tainted javascript: URL assigned to location.href.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>javascript: URL navigated via location.replace</title>
      <link>/docs/alerts/210003-11/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-11/</guid>
      <description>&lt;p&gt;Tainted javascript: URL passed to location.replace.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>javascript: URL opened via window.open</title>
      <link>/docs/alerts/210003-13/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210003-13/</guid>
      <description>&lt;p&gt;Tainted javascript: URL passed to window.open.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>LDAP Injection</title>
      <link>/docs/alerts/40015-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40015-2/</guid>
      <description>&lt;p&gt;LDAP Injection may be possible. It may be possible for an attacker to bypass authentication controls, and to view and modify arbitrary data in the LDAP directory.&lt;/p&gt;</description>
    </item>
    <item>
      <title>LDAP Injection - activedirectory</title>
      <link>/docs/alerts/40015-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40015-1/</guid>
      <description>&lt;p&gt;LDAP Injection may be possible. It may be possible for an attacker to bypass authentication controls, and to view and modify arbitrary data in the LDAP directory.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lit unsafeHTML taint flow</title>
      <link>/docs/alerts/220005-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220005-6/</guid>
      <description>&lt;p&gt;Detects dynamic client-side template compilation/rendering where attacker-controlled templates or outputs are injected into the DOM.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>NoSQL Injection - MongoDB</title>
      <link>/docs/alerts/40033/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40033/</guid>
      <description>&lt;p&gt;MongoDB query injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>NoSQL Injection - MongoDB (Time Based)</title>
      <link>/docs/alerts/90039/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90039/</guid>
      <description>&lt;p&gt;MongoDB query injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Off-site Redirect</title>
      <link>/docs/alerts/10028/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10028/</guid>
      <description>&lt;p&gt;Open redirects are one of the OWASP 2010 Top Ten vulnerabilities. This check looks at user-supplied input in query string parameters and POST data to identify where open redirects might be possible. Open redirects occur when an application allows user-supplied input (e.g. &lt;a href=&#34;https://nottrusted.com&#34;&gt;https://nottrusted.com&lt;/a&gt;) to control an off-site destination. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OS Command Injection - Unix cat /etc/passwd (pipe)</title>
      <link>/docs/alerts/200001/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200001/</guid>
      <description>&lt;p&gt;OS command injection (also known as shell injection) is a web security vulnerability that allows an attacker to execute arbitrary operating system (OS) commands on the server that is running an application, and typically fully compromise the application and all its data.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Out of Band XSS</title>
      <link>/docs/alerts/40031/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40031/</guid>
      <description>&lt;p&gt;Cross-site Scripting (XSS) is an attack technique that involves echoing attacker-supplied code into a user&amp;rsquo;s browser instance. A browser instance can be a standard web browser client, or a browser object embedded in a software product such as the browser within WinAmp, an RSS reader, or an email client. The code itself is usually written in HTML/JavaScript, but may also extend to VBScript, ActiveX, Java, Flash, or any other browser-supported technology.&#xA;When an attacker gets a user&amp;rsquo;s browser to execute his/her code, the code will run within the security context (or zone) of the hosting web site. With this level of privilege, the code has the ability to read, modify and transmit any sensitive data accessible by the browser. A Cross-site Scripted user could have his/her account hijacked (cookie theft), their browser redirected to another location, or possibly shown fraudulent content delivered by the web site they are visiting. Cross-site Scripting attacks essentially compromise the trust relationship between a user and the web site. Applications utilizing browser object instances which load content from the file system may execute code under the local machine zone allowing for system compromise.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Prototype pollution influenced fetch() init</title>
      <link>/docs/alerts/210008-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210008-1/</guid>
      <description>&lt;p&gt;A prior tainted prototype write influenced inherited fetch() init fields.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>React dangerouslySetInnerHTML taint flow</title>
      <link>/docs/alerts/220005-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220005-5/</guid>
      <description>&lt;p&gt;Detects dynamic client-side template compilation/rendering where attacker-controlled templates or outputs are injected into the DOM.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Remote Code Execution - CVE-2012-1823</title>
      <link>/docs/alerts/20018/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/20018/</guid>
      <description>&lt;p&gt;Some PHP versions, when configured to run using CGI, do not correctly handle query strings that lack an unescaped &amp;ldquo;=&amp;rdquo; character, enabling arbitrary code execution. In this case, an operating system command was caused to be executed on the web server, and the results were returned to the web browser.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Remote Code Execution - Shell Shock</title>
      <link>/docs/alerts/10048-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10048-1/</guid>
      <description>&lt;p&gt;The server is running a version of the Bash shell that allows remote attackers to execute arbitrary code.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Remote Code Execution - Shell Shock</title>
      <link>/docs/alerts/10048-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10048-2/</guid>
      <description>&lt;p&gt;The server is running a version of the Bash shell that allows remote attackers to execute arbitrary code.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Remote Code Execution (React2Shell)</title>
      <link>/docs/alerts/40048/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40048/</guid>
      <description>&lt;p&gt;The server is running Next.js and vulnerable versions of React Server Components with Next.js which allow remote attackers to execute arbitrary code.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Remote File Inclusion</title>
      <link>/docs/alerts/7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/7/</guid>
      <description>&lt;p&gt;Remote File Include (RFI) is an attack technique used to exploit &amp;ldquo;dynamic file include&amp;rdquo; mechanisms in web applications. When web applications take user input (URL, parameter value, etc.) and pass them into file include commands, the web application might be tricked into including remote files with malicious code.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Remote OS Command Injection</title>
      <link>/docs/alerts/90020/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90020/</guid>
      <description>&lt;p&gt;Attack technique used for unauthorized execution of operating system commands. This attack is possible when an application accepts untrusted input to build operating system commands in an insecure manner involving improper data sanitization, and/or improper calling of external programs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Remote OS Command Injection (Time Based)</title>
      <link>/docs/alerts/90037/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90037/</guid>
      <description>&lt;p&gt;Attack technique used for unauthorized execution of operating system commands. This attack is possible when an application accepts untrusted input to build operating system commands in an insecure manner involving improper data sanitization, and/or improper calling of external programs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Response field parsed via createContextualFragment</title>
      <link>/docs/alerts/210007-7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210007-7/</guid>
      <description>&lt;p&gt;Response-derived HTML parsed via Range.createContextualFragment.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Response field parsed via DOMParser</title>
      <link>/docs/alerts/210007-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210007-6/</guid>
      <description>&lt;p&gt;Response-derived HTML parsed via DOMParser.parseFromString.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Response field rendered via document.write</title>
      <link>/docs/alerts/210007-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210007-2/</guid>
      <description>&lt;p&gt;Response-derived data reached document.write.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Response field rendered via DOM mutation</title>
      <link>/docs/alerts/210007-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210007-5/</guid>
      <description>&lt;p&gt;Response-derived data reached DOM mutation sinks.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Response field rendered via innerHTML</title>
      <link>/docs/alerts/210007-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210007-1/</guid>
      <description>&lt;p&gt;Response-derived data reached innerHTML.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Response field rendered via insertAdjacentHTML</title>
      <link>/docs/alerts/210007-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210007-4/</guid>
      <description>&lt;p&gt;Response-derived HTML reached insertAdjacentHTML.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Response field rendered via outerHTML</title>
      <link>/docs/alerts/210007-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210007-3/</guid>
      <description>&lt;p&gt;Response-derived data reached outerHTML.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Response field rendered via setHTMLUnsafe</title>
      <link>/docs/alerts/210007-8/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210007-8/</guid>
      <description>&lt;p&gt;Response-derived HTML reached Element.setHTMLUnsafe.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Response field rendered via ShadowRoot.setHTMLUnsafe</title>
      <link>/docs/alerts/210007-9/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210007-9/</guid>
      <description>&lt;p&gt;Response-derived HTML reached ShadowRoot.setHTMLUnsafe.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review direct Axios destination usage</title>
      <link>/docs/alerts/220006-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220006-4/</guid>
      <description>&lt;p&gt;Detects client-side request destinations for beacon, EventSource, and Axios that can be influenced by attacker-controlled input.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review DOMParser.parseFromString with dynamic HTML/XML</title>
      <link>/docs/alerts/220000-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220000-4/</guid>
      <description>&lt;p&gt;Detects cases where untrusted data from the DOM (URL, element values, storage, messages, etc.) flows into HTML/JS execution sinks (e.g., innerHTML, outerHTML, document.write, string-based setTimeout, insertAdjacentHTML) without proper sanitization or encoding \u2014 enabling DOM-based cross-site scripting.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review dynamic import usage</title>
      <link>/docs/alerts/220007-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220007-3/</guid>
      <description>&lt;p&gt;Detects dynamic script, worker, and service-worker loader endpoints that can be influenced by attacker-controlled client-side data.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review EventSource constructor usage</title>
      <link>/docs/alerts/220006-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220006-3/</guid>
      <description>&lt;p&gt;Detects client-side request destinations for beacon, EventSource, and Axios that can be influenced by attacker-controlled input.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review importScripts usage</title>
      <link>/docs/alerts/220007-7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220007-7/</guid>
      <description>&lt;p&gt;Detects dynamic script, worker, and service-worker loader endpoints that can be influenced by attacker-controlled client-side data.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review jQuery getScript usage</title>
      <link>/docs/alerts/220007-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220007-1/</guid>
      <description>&lt;p&gt;Detects dynamic script, worker, and service-worker loader endpoints that can be influenced by attacker-controlled client-side data.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review sendBeacon body content</title>
      <link>/docs/alerts/220006-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220006-2/</guid>
      <description>&lt;p&gt;Detects client-side request destinations for beacon, EventSource, and Axios that can be influenced by attacker-controlled input.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review sendBeacon destination</title>
      <link>/docs/alerts/220006-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220006-1/</guid>
      <description>&lt;p&gt;Detects client-side request destinations for beacon, EventSource, and Axios that can be influenced by attacker-controlled input.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review serviceWorker.register usage</title>
      <link>/docs/alerts/220007-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220007-6/</guid>
      <description>&lt;p&gt;Detects dynamic script, worker, and service-worker loader endpoints that can be influenced by attacker-controlled client-side data.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review SharedWorker constructor usage</title>
      <link>/docs/alerts/220007-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220007-5/</guid>
      <description>&lt;p&gt;Detects dynamic script, worker, and service-worker loader endpoints that can be influenced by attacker-controlled client-side data.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review System.import usage</title>
      <link>/docs/alerts/220007-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220007-2/</guid>
      <description>&lt;p&gt;Detects dynamic script, worker, and service-worker loader endpoints that can be influenced by attacker-controlled client-side data.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review uses of appendChild</title>
      <link>/docs/alerts/220000-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220000-2/</guid>
      <description>&lt;p&gt;Detects cases where untrusted data from the DOM (URL, element values, storage, messages, etc.) flows into HTML/JS execution sinks (e.g., innerHTML, outerHTML, document.write, string-based setTimeout, insertAdjacentHTML) without proper sanitization or encoding \u2014 enabling DOM-based cross-site scripting.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review Vue v-html template usage</title>
      <link>/docs/alerts/220005-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220005-3/</guid>
      <description>&lt;p&gt;Detects dynamic client-side template compilation/rendering where attacker-controlled templates or outputs are injected into the DOM.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Review Worker constructor usage</title>
      <link>/docs/alerts/220007-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220007-4/</guid>
      <description>&lt;p&gt;Detects dynamic script, worker, and service-worker loader endpoints that can be influenced by attacker-controlled client-side data.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Server Side Code Injection - ASP Code Injection</title>
      <link>/docs/alerts/90019-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90019-2/</guid>
      <description>&lt;p&gt;A code injection may be possible including custom code that will be evaluated by the scripting engine.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Server Side Code Injection - PHP Code Injection</title>
      <link>/docs/alerts/90019-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90019-1/</guid>
      <description>&lt;p&gt;A code injection may be possible including custom code that will be evaluated by the scripting engine.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Server Side Include</title>
      <link>/docs/alerts/40009/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40009/</guid>
      <description>&lt;p&gt;Certain parameters may cause Server Side Include commands to be executed. This may allow database connection or arbitrary code to be executed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Server Side Request Forgery</title>
      <link>/docs/alerts/40046/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40046/</guid>
      <description>&lt;p&gt;The web server receives a remote address and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Server Side Template Injection</title>
      <link>/docs/alerts/90035/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90035/</guid>
      <description>&lt;p&gt;When the user input is inserted in the template instead of being used as argument in rendering is evaluated by the template engine. Depending on the template engine it can lead to remote code execution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Server Side Template Injection (Blind)</title>
      <link>/docs/alerts/90036/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90036/</guid>
      <description>&lt;p&gt;When the user input is inserted in the template instead of being used as argument in rendering is evaluated by the template engine. Depending on the template engine it can lead to remote code execution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>setInterval(string) from storage/referrer taint</title>
      <link>/docs/alerts/210018-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210018-5/</guid>
      <description>&lt;p&gt;Storage/referrer taint reached setInterval(string).&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>setTimeout(string) from storage/referrer taint</title>
      <link>/docs/alerts/210018-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210018-4/</guid>
      <description>&lt;p&gt;Storage/referrer taint reached setTimeout(string).&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>SOAP Action Spoofing</title>
      <link>/docs/alerts/90026/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90026/</guid>
      <description>&lt;p&gt;An unintended SOAP operation was executed by the server.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SOAP XML Injection</title>
      <link>/docs/alerts/90029/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90029/</guid>
      <description>&lt;p&gt;Some XML injected code has been interpreted by the server.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SPA hash DOM XSS</title>
      <link>/docs/alerts/200007/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200007/</guid>
      <description>&lt;p&gt;Tests hash-based SPA parameters (http://host/#/route?param=&amp;hellip;) for DOM XSS by mutating the hash in a dedicated attack tab and inspecting the DOM.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK DAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Spring4Shell</title>
      <link>/docs/alerts/40045/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40045/</guid>
      <description>&lt;p&gt;The application appears to be vulnerable to CVE-2022-22965 (otherwise known as Spring4Shell) - remote code execution (RCE) via data binding.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection</title>
      <link>/docs/alerts/40018/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40018/</guid>
      <description>&lt;p&gt;SQL injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - Double Quote (after)</title>
      <link>/docs/alerts/200000-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200000-4/</guid>
      <description>&lt;p&gt;A SQL injection attack consists of insertion or injection of a SQL query via the input data from the client to the application. A successful SQL injection exploit can read sensitive data from the database, modify database data (Insert/Update/Delete), execute administration operations on the database (such as shutdown the DBMS), recover the content of a given file present on the DBMS file system and in some cases issue commands to the operating system. SQL injection attacks are a type of injection attack, in which SQL commands are injected into data-plane input in order to affect the execution of predefined SQL commands.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - Double Quote (before)</title>
      <link>/docs/alerts/200000-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200000-2/</guid>
      <description>&lt;p&gt;A SQL injection attack consists of insertion or injection of a SQL query via the input data from the client to the application. A successful SQL injection exploit can read sensitive data from the database, modify database data (Insert/Update/Delete), execute administration operations on the database (such as shutdown the DBMS), recover the content of a given file present on the DBMS file system and in some cases issue commands to the operating system. SQL injection attacks are a type of injection attack, in which SQL commands are injected into data-plane input in order to affect the execution of predefined SQL commands.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - Hypersonic SQL (Time Based)</title>
      <link>/docs/alerts/40020/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40020/</guid>
      <description>&lt;p&gt;SQL injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - MsSQL (Time Based)</title>
      <link>/docs/alerts/40027/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40027/</guid>
      <description>&lt;p&gt;SQL injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - MySQL (Time Based)</title>
      <link>/docs/alerts/40019/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40019/</guid>
      <description>&lt;p&gt;SQL injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - Oracle (Time Based)</title>
      <link>/docs/alerts/40021/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40021/</guid>
      <description>&lt;p&gt;SQL injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - PostgreSQL (Time Based)</title>
      <link>/docs/alerts/40022/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40022/</guid>
      <description>&lt;p&gt;SQL injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - Single Quote (after)</title>
      <link>/docs/alerts/200000-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200000-3/</guid>
      <description>&lt;p&gt;A SQL injection attack consists of insertion or injection of a SQL query via the input data from the client to the application. A successful SQL injection exploit can read sensitive data from the database, modify database data (Insert/Update/Delete), execute administration operations on the database (such as shutdown the DBMS), recover the content of a given file present on the DBMS file system and in some cases issue commands to the operating system. SQL injection attacks are a type of injection attack, in which SQL commands are injected into data-plane input in order to affect the execution of predefined SQL commands.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - Single Quote (before)</title>
      <link>/docs/alerts/200000-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200000-1/</guid>
      <description>&lt;p&gt;A SQL injection attack consists of insertion or injection of a SQL query via the input data from the client to the application. A successful SQL injection exploit can read sensitive data from the database, modify database data (Insert/Update/Delete), execute administration operations on the database (such as shutdown the DBMS), recover the content of a given file present on the DBMS file system and in some cases issue commands to the operating system. SQL injection attacks are a type of injection attack, in which SQL commands are injected into data-plane input in order to affect the execution of predefined SQL commands.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - SQLite (Time Based)</title>
      <link>/docs/alerts/40024-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40024-1/</guid>
      <description>&lt;p&gt;SQL injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection - SQLite (Time Based)</title>
      <link>/docs/alerts/40024-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40024-2/</guid>
      <description>&lt;p&gt;SQL injection may be possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - Arithmetic Evaluation</title>
      <link>/docs/alerts/100044-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-2/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - EL Evaluation</title>
      <link>/docs/alerts/100044-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-5/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - Expression Evaluation</title>
      <link>/docs/alerts/100044-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-3/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - Quote Consumption</title>
      <link>/docs/alerts/100044-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-1/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - Template Evaluation</title>
      <link>/docs/alerts/100044-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-4/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - Unicode Byte Truncation</title>
      <link>/docs/alerts/100044-8/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-8/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - Unicode Case Conversion</title>
      <link>/docs/alerts/100044-9/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-9/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - Unicode Combining Diacritic</title>
      <link>/docs/alerts/100044-10/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-10/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - Unicode Normalisation</title>
      <link>/docs/alerts/100044-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-6/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suspicious Input Transformation - URL Decoding Error</title>
      <link>/docs/alerts/100044-7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/100044-7/</guid>
      <description>&lt;p&gt;The application performed a suspicious input transformation that may indicate a security vulnerability. The input was transformed in an unexpected way, suggesting potential issues with input validation, encoding/decoding, or expression evaluation. This could indicate vulnerabilities such as server-side template injection, expression language injection, unicode normalization issues, or other input processing flaws that may be exploitable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tainted dangerous key used in prototype write</title>
      <link>/docs/alerts/210008-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210008-2/</guid>
      <description>&lt;p&gt;Tainted data reached a dangerous prototype key write.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tainted data compiled as AngularJS template</title>
      <link>/docs/alerts/220004-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220004-2/</guid>
      <description>&lt;p&gt;Finds AngularJS code patterns where untrusted data is compiled or parsed as AngularJS expressions/templates, including $parse, $interpolate, $compile, interpolation delimiters and ng-* expression attributes.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tainted data passed to AngularJS $parse</title>
      <link>/docs/alerts/220004-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220004-1/</guid>
      <description>&lt;p&gt;Finds AngularJS code patterns where untrusted data is compiled or parsed as AngularJS expressions/templates, including $parse, $interpolate, $compile, interpolation delimiters and ng-* expression attributes.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tainted network destination URL</title>
      <link>/docs/alerts/220006-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220006-5/</guid>
      <description>&lt;p&gt;Detects client-side request destinations for beacon, EventSource, and Axios that can be influenced by attacker-controlled input.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tainted string executed via setInterval</title>
      <link>/docs/alerts/210011-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210011-2/</guid>
      <description>&lt;p&gt;Tainted string passed as the first argument to setInterval(), leading to repeated code execution.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tainted string executed via setTimeout</title>
      <link>/docs/alerts/210011-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/210011-1/</guid>
      <description>&lt;p&gt;Tainted string passed as the first argument to setTimeout(), leading to code execution.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK IAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tainted worker or script loader URL</title>
      <link>/docs/alerts/220007-8/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220007-8/</guid>
      <description>&lt;p&gt;Detects dynamic script, worker, and service-worker loader endpoints that can be influenced by attacker-controlled client-side data.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Template injection (taint flow)</title>
      <link>/docs/alerts/220005-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220005-4/</guid>
      <description>&lt;p&gt;Detects dynamic client-side template compilation/rendering where attacker-controlled templates or outputs are injected into the DOM.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Template output injected into DOM</title>
      <link>/docs/alerts/220005-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220005-2/</guid>
      <description>&lt;p&gt;Detects dynamic client-side template compilation/rendering where attacker-controlled templates or outputs are injected into the DOM.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>template.innerHTML with dynamic content</title>
      <link>/docs/alerts/220000-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/220000-5/</guid>
      <description>&lt;p&gt;Detects cases where untrusted data from the DOM (URL, element values, storage, messages, etc.) flows into HTML/JS execution sinks (e.g., innerHTML, outerHTML, document.write, string-based setTimeout, insertAdjacentHTML) without proper sanitization or encoding \u2014 enabling DOM-based cross-site scripting.&lt;/p&gt;&#xA;&lt;p&gt;Generated by OWASP PTK SAST Module&lt;/p&gt;</description>
    </item>
    <item>
      <title>Text4shell (CVE-2022-42889)</title>
      <link>/docs/alerts/40047/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/40047/</guid>
      <description>&lt;p&gt;Apache Commons Text prior to 1.10.0 allows RCE when applied to untrusted input due to insecure interpolation defaults.Apache Commons Text performs variable interpolation, allowing properties to be dynamically evaluated and expanded.The application has been shown to initial contact with remote servers via variable interpolation and may well be vulnerable to Remote Code Execution (RCE).&lt;/p&gt;</description>
    </item>
    <item>
      <title>User Controllable Charset</title>
      <link>/docs/alerts/10030/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10030/</guid>
      <description>&lt;p&gt;This check looks at user-supplied input in query string parameters and POST data to identify where Content-Type or meta tag charset declarations might be user-controlled. Such charset declarations should always be declared by the application. If an attacker can control the response charset, they could manipulate the HTML to perform XSS or other attacks. For example, an attacker controlling the &lt;!-- raw HTML omitted --&gt; element charset value is able to declare UTF-7 and is also able to include enough user-controlled payload early in the HTML document to have it interpreted as UTF-7. By encoding their payload with UTF-7 the attacker is able to bypass any server-side XSS protections and embed script in the page.&lt;/p&gt;</description>
    </item>
    <item>
      <title>User Controllable HTML Element Attribute (Potential XSS)</title>
      <link>/docs/alerts/10031/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10031/</guid>
      <description>&lt;p&gt;This check looks at user-supplied input in query string parameters and POST data to identify where certain HTML attribute values might be controlled. This provides hot-spot detection for XSS (cross-site scripting) that will require further review by a security analyst to determine exploitability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>User Controllable JavaScript Event (XSS)</title>
      <link>/docs/alerts/10043/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/10043/</guid>
      <description>&lt;p&gt;This check looks at user-supplied input in query string parameters and POST data to identify where certain HTML attribute values might be controlled. This provides hot-spot detection for XSS (cross-site scripting) that will require further review by a security analyst to determine exploitability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XML External Entity Attack</title>
      <link>/docs/alerts/90023/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90023/</guid>
      <description>&lt;p&gt;This technique takes advantage of a feature of XML to build documents dynamically at the time of processing. An XML message can either provide data explicitly or by pointing to an URI where the data exists. In the attack technique, external entities may replace the entity value with malicious data, alternate referrals or may compromise the security of the data the server/XML application has access to.&#xA;Attackers may also use External Entities to have the web services server download malicious code or content to the server for use in secondary or follow on attacks.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XPath Injection</title>
      <link>/docs/alerts/90021/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90021/</guid>
      <description>&lt;p&gt;XPath Injection is an attack technique used to exploit applications that construct XPath (XML Path Language) queries from user-supplied input to query or navigate XML documents. It can be used directly by an application to query an XML document, as part of a larger operation such as applying an XSLT transformation to an XML document, or applying an XQuery to an XML document. The syntax of XPath bears some resemblance to an SQL query, and indeed, it is possible to form SQL-like queries on an XML document using XPath.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSLT Injection</title>
      <link>/docs/alerts/90017/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/90017/</guid>
      <description>&lt;p&gt;Injection using XSL transformations may be possible, and may allow an attacker to read system information, read and write files, or execute arbitrary code.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - attribute context img onerror</title>
      <link>/docs/alerts/200002-6/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-6/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - attribute-name event injection</title>
      <link>/docs/alerts/200002-17/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-17/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - double-quoted attribute event injection</title>
      <link>/docs/alerts/200002-14/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-14/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - Img onerror</title>
      <link>/docs/alerts/200002-4/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-4/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - Img onerror</title>
      <link>/docs/alerts/200002-5/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-5/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - JS block comment break-out</title>
      <link>/docs/alerts/200002-13/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-13/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - JS expression replacement</title>
      <link>/docs/alerts/200002-10/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-10/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - JS single-quoted string break-out</title>
      <link>/docs/alerts/200002-11/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-11/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - JS slash/regex literal break-out</title>
      <link>/docs/alerts/200002-12/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-12/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - JS string break-out</title>
      <link>/docs/alerts/200002-8/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-8/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - JS template literal break-out</title>
      <link>/docs/alerts/200002-9/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-9/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - Script tag after noscript tag</title>
      <link>/docs/alerts/200002-2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-2/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - single-quoted attribute event injection</title>
      <link>/docs/alerts/200002-15/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-15/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - SVG onload polyglot</title>
      <link>/docs/alerts/200002-7/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-7/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - Svg tag with animation event</title>
      <link>/docs/alerts/200002-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-3/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - tag-name SVG onload injection</title>
      <link>/docs/alerts/200002-18/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-18/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - Unfiltered &lt;script&gt; tag</title>
      <link>/docs/alerts/200002-1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-1/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
    <item>
      <title>XSS - unquoted attribute event injection</title>
      <link>/docs/alerts/200002-16/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/alerts/200002-16/</guid>
      <description>&lt;p&gt;Reflected Cross-site Scripting (XSS) is another name for non-persistent XSS, where the attack doesn&amp;rsquo;t load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
