CVE-2022-35695
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 where malicious JavaScript can be injected through URL parameters. When a victim is tricked into visiting a specially crafted URL referencing a vulnerable page, the malicious script executes within their browser context.
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.
-
Confirm Adobe Experience Manager is installedAccess the AEM web interface and check for AEM-specific pages or login screens. AEM typically exposes version information through the system console or welcome page.Affected if AEM is not installed, this CVE does not apply.
-
Determine the installed AEM versionLocate the version information within the AEM administration interface. Common locations include the AEM welcome page, the /system/console/productinfo console (if accessible), or the 'About Adobe Experience Manager' section in the help menu.Affected if Unable to determine the version - manual inspection of AEM installation files or release notes may be required.
-
Compare against affected version rangesCheck if the installed version is below 6.5.15.0 for AEM or below 2022.10.0 for AEM Cloud Service. Any version below these thresholds is affected by this reflected XSS vulnerability.Affected if The installed version is below 6.5.15.0 (AEM) or below 2022.10.0 (Cloud Service).
-
Understand the attack vectorNote that this is a reflected XSS vulnerability via URL parameters. The flaw exists when user-supplied input in URL parameters is reflected back in the page response without proper encoding. There is no specific module or feature to enable/disable - the vulnerability is present in how the application handles URL parameters.Affected if The vulnerability applies to any AEM instance below the patched versions, regardless of configuration, since it stems from how URL parameters are processed.
You are affected if your installed Adobe Experience Manager version is below 6.5.15.0 (for AEM) or below 2022.10.0 (for AEM Cloud Service), as these versions contain the fix for the reflected XSS in URL parameters.
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
Upgrade to Adobe Experience Manager version 6.5.15 or later to obtain the security patch. Additionally, implement output encoding and input validation on all user-supplied parameters.
AEM 6.5.15.0+ or AEM Cloud Service 2022.10.0+
- For Adobe Experience Manager on-premises: Upgrade to version 6.5.15.0 or later
- For Adobe Experience Manager Cloud Service: Upgrade to version 2022.10.0 or later
- After upgrading, verify that the XSS vulnerability is resolved by testing with the previously vulnerable URL patterns
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35695 — 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-35695 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