Apache Wicket JavaScriptUtils Escape Bypass Remote Script Execution Vulnerability (CVE-2026-83559)
Executive & SecOps Summary
SECOPS ASSESSMENTApache Wicket versions 8.0.0 to 8.19.0, 9.0.0 to 9.24.0, 10.0.0 to 10.11.0, and unsupported 7.x or older versions
Attackers can bypass the escaping logic by combining backslashes and quotes, leading to arbitrary JavaScript execution (XSS) within the victim's browser session
Immediately upgrade to the patched versions: 8.20.0, 9.25.0, or 10.12.0 depending on your current release branch
Affected Products & Version Scope
Remediation & Live Workaround Commands
PATCH & WORKAROUND1. Official Patch & Version Upgrade Commands
Update your project's build configuration (pom.xml or build.gradle) to use the patched versions of Apache Wicket.
For Maven (pom.xml):
<!-- Upgrade Apache Wicket dependencies to secure versions -->
<dependency>
<groupId>org.apache.wicket</groupId>
<artifactId>wicket-core</artifactId>
<version>10.12.0</version> <!-- Or 9.25.0, 8.20.0 depending on your branch -->
</dependency>
<dependency>
<groupId>org.apache.wicket</groupId>
<artifactId>wicket-extensions</artifactId>
<version>10.12.0</version>
</dependency>For Gradle (build.gradle):
implementation 'org.apache.wicket:wicket-core:10.12.0'
implementation 'org.apache.wicket:wicket-extensions:10.12.0'2. Temporary Workaround & Hardening Configuration
If an immediate upgrade is not feasible, implement an input validation filter to reject any input containing backslashes before they reach the vulnerable escapeQuotes() method.
Servlet Filter for Input Sanitization:
import javax.servlet.*;
import javax.servlet.http.HttpServletRequest;
import java.io.IOException;
public class SecuritySanitizationFilter implements Filter {
@Override
public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain)
throws IOException, ServletException {
HttpServletRequest httpRequest = (HttpServletRequest) request;
for (String values : httpRequest.getParameterMap().values()) {
for (String val : values) {
if (val != null && val.contains("\\")) {
throw new SecurityException('Request blocked: Backslash character detected in input.');
}
}
}
chain.doFilter(request, response);
}
}3. Log Audit & IoC Verification Commands
Scan your codebase and dependency tree to identify vulnerable versions and usages of the affected method.
Dependency and Code Scanning Commands:
# 1. Check for vulnerable Wicket versions in Maven dependency tree
mvn dependency:tree | grep -E 'wicket-core|wicket-extensions'
# 2. Search for direct invocations of the vulnerable method in your source code
grep -rn 'JavaScriptUtils.escapeQuotes' ./src/Scan Your Repositories for Transitive Vulnerable Dependencies in 30 Seconds
Automatically detect vulnerable packages across npm, PyPI, Maven, and Go, and open automated fix Pull Requests without breaking your build.
Technical Root Cause & Exploitation Mechanics
1. Vulnerability Overview & Root Cause
This vulnerability stems from improper output encoding and escaping (CWE-116) within the org.apache.wicket.core.util.string.JavaScriptUtils#escapeQuotes() method in the Apache Wicket framework. The method is designed to escape single (') and double (") quotes by prepending a backslash (\) so that the value can be safely embedded inside a JavaScript string literal. However, it fails to escape the backslash character itself first. Because the backslash is the very character that defines the escaping context, omitting its own escaping completely breaks the sanitization logic when a backslash is already present in the input.
2. Exploitation Mechanics & Attack Scenario
When an attacker supplies an input containing a backslash immediately followed by a quote (e.g., \" or \\'), the escapeQuotes() method inserts another backslash before the quote, resulting in \\". In JavaScript, the first backslash escapes the second backslash, leaving the quote itself unescaped. This unescaped quote prematurely terminates the string literal. Any subsequent payload injected by the attacker is then interpreted and executed as active JavaScript code rather than plain text, running under the application's origin and the victim's active session. This is highly exploitable in components like AjaxEditableLabel, which dynamically write error feedback messages into single-quoted JavaScript string literals.
3. Infrastructure & Business Impact
Successful exploitation of this vulnerability allows for Cross-Site Scripting (XSS). Attackers can hijack user sessions by stealing session tokens, perform unauthorized actions on behalf of authenticated users (CSRF), deface the web application, or redirect users to malicious phishing sites. This poses a severe risk to data confidentiality and integrity, potentially leading to regulatory non-compliance and loss of customer trust.
Official Vendor Advisories & References
Improper encoding or escaping of output in Apache Wicket. org.apache.wicket.core.util.string.JavaScriptUtils#escapeQuotes() replaces each single quote in its input with a backslash and a single quote, and each double quote with a backslash and a double quote, so that the value can be placed inside a JavaScript string literal. It does not escape the backslash, which is the character that has to be escaped, and escaped first, for the rest of that escaping to hold. A value that already holds a backslash immediately before a quote therefore ends up with two backslashes in front of that quote: the first escapes the second, the quote itself is left unescaped, and it closes the literal. Whatever the value carries after that point is no longer text but JavaScript, and it runs in the application's origin and in the session of the user looking at the page. The method is public, is not deprecated, and its documentation states that its result can be part of a JavaScript call such as an alert; the only limitation it notes concerns JSON values, which need different escaping. An application is affected wherever it calls the method itself and places the result inside a JavaScript string literal, from its own code or from a component of its own or of a third party, and the value it escapes holds data an attacker can influence. There is no further condition, and no component of Wicket has to be involved: the application is using the method for what its documentation offers, and the method does not deliver it. Two components shipped with Wicket Extensions pass a value through the method. org.apache.wicket.extensions.ajax.markup.html.AjaxEditableLabel writes the editor's first error feedback message into a single-quoted JavaScript string literal in the Ajax response, so an application is affected through that component where the message shown for a failed edit holds data an attacker can influence, whether that is the submitted value itself or another variable the application sets on the validation error. A validation message can carry the submitted value, because input is a message variable that every form component supplies for its own validation errors, and the documentation shows overriding a validator's message to include it; none of the message bundles shipped with Wicket interpolates it, so an application that has not written such a message is not affected through this component. org.apache.wicket.extensions.ajax.markup.html.repeater.AjaxListPanel passes the serialized markup tag of an appended component through the method and is not affected: the tag comes from the panel's own markup file, and a quote in any of its attribute values, the component's markup id included, is written as a character reference by the tag serialization and cannot close the literal. This issue affects Apache Wicket: from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, from 10.0.0 through 10.11.0. Users of Apache Wicket 7.x or older, which are no longer supported, should upgrade to a supported version. Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.
Frequently Asked SecOps Questions (CVE-2026-83559)
FAQQ1. How critical is CVE-2026-83559 and is it actively exploited in the wild?
CVE-2026-83559 is rated CVSS 7.4 (HIGH) with a 30-day EPSS exploitation probability of 0.3%. Organizations running affected versions should prioritize patching based on network exposure.
Q2. Which vendors and products are affected by CVE-2026-83559?
Primary impacted vendors include apache across wicket. Scope summary: Apache Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, 10.0.0 through 10.11.0, and all unsupported 7.x or older versions
Q3. What temporary mitigations or workarounds exist for CVE-2026-83559 before patching?
[Mitigation] Immediately upgrade to the patched versions: 8.20.0, 9.25.0, or 10.12.0 depending on your current release branch Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.
Generate an Internal Engineering Notice or CISO Report for CVE-2026-83559
Instantly format this advisory into an executive CISO summary or engineering patch ticket.
🔗 Related Advisories in Similar Stack (apache)
View Category →Apache Wicket AjaxNewWindowNotifyingBehavior Cross-Site Scripting (XSS) Vulnerability (CVE-2026-82956)
[Affected Scope] Apache Wicket versions 8.0.0 to 8.19.0, 9.0.0 to 9.24.0, and 10.0.0 to 10.11.0, specifically when AjaxNewWindowNotifyingBehavior is explicitly used
Apache Wicket SmartLinkLabel Cross-Site Scripting (XSS) Vulnerability (CVE-2026-83539)
[Affected Scope] Apache Wicket versions 8.0.0 to 8.19.0, 9.0.0 to 9.24.0, and 10.0.0 to 10.11.0 utilizing SmartLinkLabel or SmartLinkMultiLineLabel components
Apache Wicket Cross-Site Scripting (XSS) Vulnerability due to Missing Resource Bundle Escaping (CVE-2026-111089)
[Affected Scope] Apache Wicket versions 8.0.0 to 8.19.0, 9.0.0 to 9.24.0, and 10.0.0 to 10.11.0
Apache Wicket WebSocket Resource Missing Authorization Vulnerability (CVE-2026-82115) Analysis & Mitigation Guide
[Affected Scope] Apache Wicket versions 8.0.0 to 8.19.0, 9.0.0 to 9.24.0, 10.0.0 to 10.11.0, and unsupported 7.x releases
Subscribe to Daily Vulnerability Briefings & KEV Alerts
Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.