- Help - Russian
+ Help - Russian
-
+
@@ -1988,7 +1994,7 @@
ZAP Marketplace
help_ru_RU
- 2
+ 3
release
@@ -1997,20 +2003,20 @@
ZAP Marketplace
ZAP Crowdin Team
- 2022-02-24
+ 2025-08-21
- Help - Spanish
+ Help - Spanish
-
+
@@ -2021,7 +2027,7 @@
ZAP Marketplace
help_es_ES
- 10
+ 11
release
@@ -2030,20 +2036,20 @@
ZAP Marketplace
ZAP Crowdin Team
- 2022-01-18
+ 2025-08-21
- Help - Turkish
+ Help - Turkish
-
+
@@ -2054,7 +2060,7 @@
ZAP Marketplace
help_tr_TR
- 2
+ 3
release
@@ -2063,7 +2069,7 @@
ZAP Marketplace
ZAP Crowdin Team
- 2022-01-18
+ 2025-08-21
@@ -2142,7 +2148,7 @@
ZAP Marketplace
-
+
@@ -2155,16 +2161,16 @@
ZAP Marketplace
imagelocationscanner
- 5
+ 7
beta
- Jay Ball (veggiespam) and the ZAP Dev Team
+ Jay Ball (@veggiespam) and the ZAP Dev Team
- 2024-04-11
+ 2025-09-18
@@ -2177,7 +2183,7 @@
ZAP Marketplace
-
+
@@ -2190,7 +2196,7 @@
ZAP Marketplace
exim
- 0.13.0
+ 0.15.0
beta
@@ -2199,7 +2205,7 @@
ZAP Marketplace
ZAP Dev Team & thatsn0tmysite
- 2025-01-09
+ 2025-09-02
@@ -2379,7 +2385,7 @@
ZAP Marketplace
-
+
@@ -2392,7 +2398,7 @@
ZAP Marketplace
webdriverlinux
- 129
+ 163
release
@@ -2401,7 +2407,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-03-11
+ 2025-10-22
@@ -2414,7 +2420,7 @@
ZAP Marketplace
-
+
@@ -2427,7 +2433,7 @@
ZAP Marketplace
webdrivermacos
- 129
+ 163
release
@@ -2436,7 +2442,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-03-11
+ 2025-10-22
@@ -2515,7 +2521,7 @@
ZAP Marketplace
-
+
@@ -2528,7 +2534,7 @@
ZAP Marketplace
network
- 0.21.0
+ 0.23.0
beta
@@ -2537,7 +2543,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-03-04
+ 2025-09-02
@@ -2550,7 +2556,7 @@
ZAP Marketplace
-
+
@@ -2563,7 +2569,7 @@
ZAP Marketplace
oast
- 0.21.0
+ 0.22.0
beta
@@ -2572,7 +2578,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-01-09
+ 2025-06-20
@@ -2620,7 +2626,7 @@
ZAP Marketplace
-
+
@@ -2633,7 +2639,7 @@
ZAP Marketplace
openapi
- 44
+ 46
beta
@@ -2642,7 +2648,7 @@
ZAP Marketplace
ZAP Dev Team plus Joanna Bona, Nathalie Bouchahine, Artur Grzesica, Mohammad Kamar, Markus Kiss, Michal Materniak, Marcin Spiewak, and SDA SE Open Industry Solutions
- 2025-01-09
+ 2025-09-10
@@ -2690,7 +2696,7 @@
ZAP Marketplace
-
+
@@ -2703,7 +2709,7 @@
ZAP Marketplace
pscan
- 0.2.0
+ 0.5.0
alpha
@@ -2712,7 +2718,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-02-12
+ 2025-09-10
@@ -2725,7 +2731,7 @@
ZAP Marketplace
-
+
@@ -2738,7 +2744,7 @@
ZAP Marketplace
pscanrules
- 63
+ 68
release
@@ -2747,7 +2753,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-03-04
+ 2025-10-21
@@ -2760,7 +2766,7 @@
ZAP Marketplace
-
+
@@ -2773,7 +2779,7 @@
ZAP Marketplace
pscanrulesAlpha
- 44
+ 46
alpha
@@ -2782,7 +2788,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-03-04
+ 2025-09-18
@@ -2795,7 +2801,7 @@
ZAP Marketplace
-
+
@@ -2808,7 +2814,7 @@
ZAP Marketplace
pscanrulesBeta
- 43
+ 46
beta
@@ -2817,7 +2823,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-03-04
+ 2025-09-18
@@ -2863,7 +2869,7 @@
ZAP Marketplace
-
+
@@ -2876,7 +2882,7 @@
ZAP Marketplace
postman
- 0.6.0
+ 0.7.0
alpha
@@ -2885,7 +2891,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-02-03
+ 2025-09-02
@@ -2933,7 +2939,7 @@
ZAP Marketplace
-
+
@@ -2946,7 +2952,7 @@
ZAP Marketplace
quickstart
- 51
+ 52
release
@@ -2955,7 +2961,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-01-10
+ 2025-07-10
@@ -3069,7 +3075,7 @@
ZAP Marketplace
-
+
@@ -3082,7 +3088,7 @@
ZAP Marketplace
reports
- 0.38.0
+ 0.41.0
release
@@ -3091,7 +3097,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-03-04
+ 2025-09-04
@@ -3174,7 +3180,7 @@
ZAP Marketplace
-
+
@@ -3187,7 +3193,7 @@
ZAP Marketplace
retire
- 0.45.0
+ 0.49.0
release
@@ -3196,7 +3202,7 @@
ZAP Marketplace
Nikita Mundhada and the ZAP Dev Team
- 2025-03-04
+ 2025-09-18
@@ -3209,7 +3215,7 @@
ZAP Marketplace
-
+
@@ -3222,7 +3228,7 @@
ZAP Marketplace
reveal
- 9
+ 10
release
@@ -3231,7 +3237,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-01-10
+ 2025-06-20
@@ -3244,7 +3250,7 @@
ZAP Marketplace
-
+
@@ -3257,7 +3263,7 @@
ZAP Marketplace
revisit
- 5
+ 6
alpha
@@ -3266,7 +3272,7 @@
ZAP Marketplace
ZAP Dev Team
- 2023-10-23
+ 2025-06-20
@@ -3345,7 +3351,7 @@
ZAP Marketplace
-
+
@@ -3358,7 +3364,7 @@
ZAP Marketplace
scanpolicies
- 0.2.0
+ 0.5.0
alpha
@@ -3367,7 +3373,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-01-10
+ 2025-09-18
@@ -3380,7 +3386,7 @@
ZAP Marketplace
-
+
@@ -3393,7 +3399,7 @@
ZAP Marketplace
scripts
- 45.8.0
+ 45.14.0
release
@@ -3402,7 +3408,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-01-10
+ 2025-10-07
@@ -3415,7 +3421,7 @@
ZAP Marketplace
-
+
@@ -3428,7 +3434,7 @@
ZAP Marketplace
selenium
- 15.35.0
+ 15.41.0
release
@@ -3437,7 +3443,7 @@
ZAP Marketplace
ZAP Dev Team
- 2025-03-11
+ 2025-10-21
@@ -3520,7 +3526,7 @@
ZAP Marketplace
-
+
@@ -3533,7 +3539,7 @@
ZAP Marketplace
soap
- 24
+ 28
beta
@@ -3542,7 +3548,40 @@
ZAP Marketplace
Alberto (albertov91) + ZAP Dev Team
- 2025-01-10
+ 2025-09-18
+
+
+
+
+
+
+ Software Risk Manager Extension
+
+
+
+
+
+
+
+
+
+
+ Includes request and response data in XML reports and provides the ability to upload reports directly to a Software Risk Manager server
+
-
+
diff --git a/alerttags/custom_payloads/index.xml b/alerttags/custom_payloads/index.xml
index ee62daf31e..591ffbb090 100644
--- a/alerttags/custom_payloads/index.xml
+++ b/alerttags/custom_payloads/index.xml
@@ -49,5 +49,12 @@
/docs/alerts/10057/<p>A hash of a username (admin) was found in the response. This may indicate that the application is subject to an Insecure Direct Object Reference (IDOR) vulnerability. Manual testing will be required to see if this discovery can be abused.</p>
+
+ XPath Injection
+ /docs/alerts/90021/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/90021/
+ <p>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.</p>
+
diff --git a/alerttags/cve-2012-1823/index.html b/alerttags/cve-2012-1823/index.html
index 9ffcbb20dc..d4cf5e98e0 100644
--- a/alerttags/cve-2012-1823/index.html
+++ b/alerttags/cve-2012-1823/index.html
@@ -24,7 +24,7 @@
-
+
@@ -212,7 +212,7 @@
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.
+
+
+
+
Solution
+ If at all possible, use library calls rather than external processes to recreate the desired functionality. Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by your software. OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows you to specify restrictions on file operations. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the command locally in the session's state instead of sending it out to the client in a hidden form field. Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using the ESAPI Encoding control or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error. If you need to use dynamically-generated query strings or commands in spite of the risk, properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allow list (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection. If the program to be executed allows arguments to be specified within an input file or from standard input, then consider using that mode to pass arguments instead of the command line. If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. Some languages offer multiple functions that can be used to invoke commands. Where possible, identify any function that invokes a command shell using a single string, and replace it with a function that requires individual arguments. These functions typically perform appropriate quoting and filtering of arguments. For example, in C, the system() function accepts a string that contains the entire command to be executed, whereas execl(), execve(), and others require an array of strings, one for each argument. In Windows, CreateProcess() only accepts one command at a time. In Perl, if system() is provided with an array of arguments, then it will quote each of the arguments. Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use an allow list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a deny list). However, deny lists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if you are expecting colors such as "red" or "blue." When constructing OS command strings, use stringent allow lists that limit the character set based on the expected value of the parameter in the request. This will indirectly limit the scope of an attack, but this technique is less important than proper output encoding and escaping. Note that proper output encoding, escaping, and quoting is the most effective solution for preventing OS command injection, although input validation may provide some defense-in-depth. This is because it effectively limits what will appear in output. Input validation will not always prevent OS command injection, especially if you are required to support free-form text fields that could contain arbitrary characters. For example, when invoking a mail program, you might need to allow the subject field to contain otherwise-dangerous inputs like ";" and ">" characters, which would need to be escaped or otherwise handled. In this case, stripping the character might reduce the risk of OS command injection, but it would produce incorrect behavior because the subject field would not be recorded as the user intended. This might seem to be a minor inconvenience, but it could be more important when the program relies on well-structured subject lines in order to pass messages to other components. Even if you make a mistake in your validation (such as forgetting one out of 100 input fields), appropriate encoding is still likely to protect you from injection-based attacks. As long as it is not done in isolation, input validation is still a useful technique, since it may significantly reduce your attack surface, allow you to detect some attacks, and provide other security benefits that proper encoding does not address.
+
+
+
Other Info
+ The scan rule was able to control the timing of the application response by sending [sleep 5] to the operating system running this application.
+
-
+
diff --git a/docs/alerts/index.xml b/docs/alerts/index.xml
index 24071da5ee..6a7c97686f 100644
--- a/docs/alerts/index.xml
+++ b/docs/alerts/index.xml
@@ -69,7 +69,7 @@
/docs/alerts/90018/
Mon, 01 Jan 0001 00:00:00 +0000/docs/alerts/90018/
- <p>A SQL injection may be possible using the attached payload</p>
+ <p>A SQL injection may be possible using the attached payload.</p>Anti-clickjacking Header
@@ -449,6 +449,13 @@
/docs/alerts/10055/
+
+ CSP: Failure to Define Directive with No Fallback
+ /docs/alerts/10055-13/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/10055-13/
+ <p>The Content Security Policy fails to define one of the directives that has no fallback. Missing/excluding them is the same as allowing anything.</p>
+ CSP: Header & Meta
/docs/alerts/10055-12/
@@ -580,7 +587,7 @@
/docs/alerts/10032-2/
Mon, 01 Jan 0001 00:00:00 +0000/docs/alerts/10032-2/
- <p>The following emails were found being serialized in the viewstate field:</p>
+ <p>Email addresses were found being serialized in the viewstate field.</p>Exponential Entity Expansion (Billion Laughs Attack)
@@ -1184,6 +1191,13 @@
/docs/alerts/10038-2/<p>The “X-Content-Security-Policy” and “X-WebKit-CSP” headers are no longer recommended.</p>
+
+ Off-site Redirect
+ /docs/alerts/10028/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/10028/
+ <p>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. <a href="https://nottrusted.com">https://nottrusted.com</a>) 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.</p>
+ Old Asp.Net Version in Use
/docs/alerts/10032-3/
@@ -1191,13 +1205,6 @@
/docs/alerts/10032-3/<p>This website uses ASP.NET version 1.0 or 1.1.</p>
-
- Open Redirect
- /docs/alerts/10028/
- Mon, 01 Jan 0001 00:00:00 +0000
- /docs/alerts/10028/
- <p>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. <a href="https://nottrusted.com">https://nottrusted.com</a>) to control an offsite redirect. This is generally a pretty accurate way to find where 301 or 302 redirects could be exploited by spammers or phishing attacks.</p>
- Out of Band XSS
/docs/alerts/40031/
@@ -1294,7 +1301,7 @@
/docs/alerts/10032-1/
Mon, 01 Jan 0001 00:00:00 +0000/docs/alerts/10032-1/
- <p>The following potential IP addresses were found being serialized in the viewstate field:</p>
+ <p>Potential IP addresses were found being serialized in the viewstate field.</p>Private IP Disclosure
@@ -1401,6 +1408,13 @@
/docs/alerts/90020/<p>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.</p>
+
+ Remote OS Command Injection (Time Based)
+ /docs/alerts/90037/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/90037/
+ <p>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.</p>
+ Retrieved from Cache
/docs/alerts/10050-1/
@@ -1724,42 +1738,42 @@
<p>SQL injection may be possible.</p>
- SQL Injection - Hypersonic SQL
+ SQL Injection - Hypersonic SQL (Time Based)
/docs/alerts/40020/
Mon, 01 Jan 0001 00:00:00 +0000/docs/alerts/40020/<p>SQL injection may be possible.</p>
- SQL Injection - MsSQL
+ SQL Injection - MsSQL (Time Based)
/docs/alerts/40027/
Mon, 01 Jan 0001 00:00:00 +0000/docs/alerts/40027/<p>SQL injection may be possible.</p>
- SQL Injection - MySQL
+ SQL Injection - MySQL (Time Based)
/docs/alerts/40019/
Mon, 01 Jan 0001 00:00:00 +0000/docs/alerts/40019/<p>SQL injection may be possible.</p>
- SQL Injection - Oracle
+ SQL Injection - Oracle (Time Based)
/docs/alerts/40021/
Mon, 01 Jan 0001 00:00:00 +0000/docs/alerts/40021/<p>SQL injection may be possible.</p>
- SQL Injection - PostgreSQL
+ SQL Injection - PostgreSQL (Time Based)
/docs/alerts/40022/
Mon, 01 Jan 0001 00:00:00 +0000/docs/alerts/40022/<p>SQL injection may be possible.</p>
- SQL Injection - SQLite
+ SQL Injection - SQLite (Time Based)
/docs/alerts/40024/
Mon, 01 Jan 0001 00:00:00 +0000/docs/alerts/40024/
@@ -1849,6 +1863,83 @@
/docs/alerts/90003/<p>The integrity attribute is missing on a script or link tag served by an external server. The integrity tag prevents an attacker who have gained access to this server from injecting a malicious content.</p>
+
+ Suspicious Input Transformation
+ /docs/alerts/100044/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044/
+
+
+
+ Suspicious Input Transformation - Arithmetic Evaluation
+ /docs/alerts/100044-2/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-2/
+ <p>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.</p>
+
+
+ Suspicious Input Transformation - EL Evaluation
+ /docs/alerts/100044-5/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-5/
+ <p>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.</p>
+
+
+ Suspicious Input Transformation - Expression Evaluation
+ /docs/alerts/100044-3/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-3/
+ <p>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.</p>
+
+
+ Suspicious Input Transformation - Quote Consumption
+ /docs/alerts/100044-1/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-1/
+ <p>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.</p>
+
+
+ Suspicious Input Transformation - Template Evaluation
+ /docs/alerts/100044-4/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-4/
+ <p>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.</p>
+
+
+ Suspicious Input Transformation - Unicode Byte Truncation
+ /docs/alerts/100044-8/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-8/
+ <p>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.</p>
+
+
+ Suspicious Input Transformation - Unicode Case Conversion
+ /docs/alerts/100044-9/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-9/
+ <p>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.</p>
+
+
+ Suspicious Input Transformation - Unicode Combining Diacritic
+ /docs/alerts/100044-10/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-10/
+ <p>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.</p>
+
+
+ Suspicious Input Transformation - Unicode Normalisation
+ /docs/alerts/100044-6/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-6/
+ <p>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.</p>
+
+
+ Suspicious Input Transformation - URL Decoding Error
+ /docs/alerts/100044-7/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/100044-7/
+ <p>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.</p>
+ Tech Detection Passive Scanner
/docs/alerts/10004/
@@ -2073,5 +2164,12 @@
/docs/alerts/90017/<p>Injection using XSL transformations may be possible, and may allow an attacker to read system information, read and write files, or execute arbitrary code.</p>
+
+ ZAP is Out of Date
+ /docs/alerts/10116/
+ Mon, 01 Jan 0001 00:00:00 +0000
+ /docs/alerts/10116/
+ <p>The version of ZAP you are using to test your app is out of date and is no longer being updated.
The risk level is set based on how out of date your ZAP version is.</p>
+
diff --git a/docs/api/includes/apis b/docs/api/includes/apis
index 301bf2ad6f..d3f30d362f 100644
--- a/docs/api/includes/apis
+++ b/docs/api/includes/apis
@@ -1991,7 +1991,7 @@ curl -X GET http://zap/JSON/ajaxSpider/action/setOptionC
GET /JSON/ajaxSpider/action/setOptionClickDefaultElems/
-
Sets whether or not the the AJAX Spider will only click on the default HTML elements.
+
Sets whether or not the AJAX Spider will only click on the default HTML elements.
Parameters
@@ -2135,6 +2135,97 @@ curl -X GET http://zap/JSON/ajaxSpider/action/setOptionC
+
+
ajaxSpiderActionSetOptionEnableExtensions
+
+
+
+
Code samples
+
+
# You can also use wget
+curl -X GET http://zap/JSON/ajaxSpider/action/setOptionEnableExtensions/?Boolean=true\
+ -H'Accept: application/json'
+
+