SlingApplication · Apache
CVE-2016-5394
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the XSS Protection API module before 1.0.12 in Apache Sling, the encoding done by the XSSAPI.encodeForJSString() method is not restrictive enough and for some input patterns allows script tags to pass through unencoded, leading to potential XSS vulnerabilities.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe XSSAPI.encodeForJSString() method in Apache Sling's XSS Protection API module before version 1.0.12 does not properly encode script tags, allowing them to pass through unencoded and creating potential XSS vulnerabilities in applications using this method.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SlingApplication
< 1.0.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Sling XSS Protection API installationLocate the sling-xssprotection-api or similar JAR file in your application's lib, WEB-INF/lib, or OSGi bundle directory. Alternatively, check your Maven/Gradle dependency tree for org.apache.sling.xss:com.apache.sling.xss or similar artifact.Affected if The Apache Sling XSS Protection API module is present in the environment
-
Determine the installed version of the XSS Protection API moduleInspect the JAR file manifest (META-INF/MANIFEST.MF) for the Bundle-Version attribute, or check your dependency management system for the exact version of the org.apache.sling.xss artifact.Affected if The version is less than 1.0.12
-
Search for usage of encodeForJSString() in application codeSearch source code repositories and deployed files for calls to XSSAPI.encodeForJSString() or xssAPI.encodeForJSString(). Also search for imports of XSSAPI-related classes.Affected if The method encodeForJSString() is being called in the codebase
-
Verify output context is JavaScriptReview where the result of encodeForJSString() is used - check if the output is placed inside a JavaScript context such as within <script> tags, event handlers, or JSON data consumed by JavaScript.Affected if The encoded output is rendered in a JavaScript context (inline script, event handler, or similar)
-
Test for script tag bypassInvoke encodeForJSString() with a test input containing <script>alert(1)</script> and inspect the output. If the script tags appear unencoded (not as \x3Cscript\x3E or similar), the vulnerability is present.Affected if The output contains unencoded <script> tags
You are affected if Apache Sling XSS Protection API module version less than 1.0.12 is installed AND your application uses encodeForJSString() to sanitize input rendered in JavaScript contexts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.12
Upgrade the Apache Sling XSS Protection API module to version 1.0.12 or later, and verify that all uses of encodeForJSString() now properly encode script content.
Fix this in Sling
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5394 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-5394 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data