CVE-2017-11296
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 · uneditedAn issue was discovered in Adobe Experience Manager 6.3, 6.2, 6.1, 6.0. A cross-site scripting vulnerability in Apache Sling Servlets Post 2.3.20 has been resolved in Adobe Experience Manager.
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 · moderate confidenceCross-site scripting (XSS) vulnerability in Apache Sling Servlets Post 2.3.20 within Adobe Experience Manager versions 6.3, 6.2, 6.1, and 6.0. The vulnerability allows injection of malicious scripts through the servlet's input handling.
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= 6.0.0= 6.1.0= 6.2.0= 6.3.0CVSS 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.0/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 installed Adobe Experience Manager versionAccess the AEM Web Console (usually at /system/console/status-html) or check the manifest file in crx-quickstart/org.apache.sling.jar. The version is also visible on the welcome page or can be queried via the CRXDE Lite console by reading the /libs/granite/core/version node.Affected if The installed version equals 6.0.0, 6.1.0, 6.2.0, or 6.3.0 exactly.
-
Locate Apache Sling Servlets Post bundle versionIn the AEM Web Console, navigate to the Bundles section (system/console/bundles) and locate the bundle named 'Apache Sling Servlets Post' or similar Sling servlets bundle. Check the Version column.Affected if The bundle version is 2.3.20.
-
Verify Sling Post Servlet endpoint is exposedCheck if the Sling Post Servlet is accessible by attempting a POST request to /bin/querybuilder.json or reviewing the servlet mappings in the OSGi console under 'Servlets' (system/console/servlets). Confirm the SlingPostServlet is registered and active.Affected if The Sling Post Servlet is registered and active, accepting user input.
-
Review servlet input handling configurationIn the OSGi Web Console (system/console/config), locate the configuration for 'Apache Sling GET Servlet' or 'Day CQ WCM Page Manager' settings that control input sanitization. Check if input validation is disabled or if HTML sanitization is not enforced.Affected if Input validation is disabled or HTML sanitization rules are not applied to the servlet input handling.
You are affected if Adobe Experience Manager version is exactly 6.0.0, 6.1.0, 6.2.0, or 6.3.0 AND the Apache Sling Servlets Post servlet is active and processing user input without proper XSS sanitization.
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 dataApply the Adobe security update for this CVE or upgrade to a patched version of Adobe Experience Manager.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11296 — 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-2017-11296 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