CVE-2022-35696
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 · uneditedAdobe Experience Manager version 6.5.14 (and earlier) is affected by a reflected Cross-Site Scripting (XSS) vulnerability. If a low-privileged attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser.
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 confidenceAdobe Experience Manager versions 6.5.14 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability. Attackers can craft malicious URLs containing JavaScript payloads in parameters that get reflected back to the victim's browser without proper sanitization, executing in the context of the victim's session.
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.5.15.0< 2022.10.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check AEM versionNavigate to the AEM Welcome page or access /system/console/configmgr and locate the 'Adobe Experience Manager' or 'Day CQ Information' section to view the installed product versionAffected if Version is below 6.5.15.0 for on-premise AEM or below 2022.10.0 for AEM Cloud Service
-
Identify endpoints accepting URL parametersReview the application's accessible URLs and identify endpoints that accept query string parameters (look for '?' and '&' in URLs). Common areas include content pages, search functions, and form handlersAffected if Endpoints exist that accept user-supplied parameters without known sanitization
-
Test for reflected parameter reflectionAppend a benign test string such as 'testxss=<script>alert(1)</script>' to suspected endpoint URLs and observe if this literal string appears unescaped in the page responseAffected if The test payload renders as literal text or executes JavaScript in the browser response without being HTML-encoded
-
Verify output encoding on reflected parametersInspect the HTTP response and page source for any URL parameter values that appear in the response. Check if special characters like <, >, ', " are converted to HTML entities (e.g., <, >)Affected if Parameter values are reflected in the response without HTML entity encoding
You are affected if your AEM version is below 6.5.15.0 (on-premise) or below 2022.10.0 (Cloud Service) AND URL parameters are reflected back in responses without proper HTML encoding.
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.
dbcve · scoped6.5.15.02022.10.0
Apply available Adobe security patches for AEM 6.5.15 or later. Until patched, implement URL parameter validation and output encoding on affected endpoints, and consider deploying a WAF to filter malicious requests.
Adobe Experience Manager 6.5.15.0+ (on-premise) or AEM Cloud Service 2022.10.0+
- Identify current Adobe Experience Manager version in use (check /system/console/systeminfo or Version screen in AEM)
- If using AEM 6.5.x, plan upgrade to 6.5.15.0 or later; if using AEM Cloud Service, plan upgrade to version 2022.10.0 or later
- Review Adobe's upgrade documentation and release notes for 6.5.15.0 to understand changes
- Test the upgrade in a non-production environment first
- Perform the upgrade following Adobe's recommended upgrade procedure
- After upgrade, verify the XSS fix by testing the previously vulnerable endpoint(s)
- Validate that all custom code and integrations work correctly post-upgrade
- Deploy the upgraded version to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35696 — 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-2022-35696 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