CVE-2022-35697
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 Core Components version 2.20.6 (and earlier) is affected by a reflected Cross-Site Scripting (XSS) vulnerability. If an 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. Exploitation of this issue requires a low author privilege access.
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 Core Components versions 2.20.6 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability. Attackers can craft malicious URLs that, when visited by an authenticated victim with low author privileges, execute arbitrary JavaScript within the victim's browser 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<= 2.20.6CVSS 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 runningAccess the AEM login page or check if the application responds on the expected host and port (commonly 4502 for author or 80/443 for publish). Look for AEM-specific identifiers in the response headers or page content.Affected if AEM is accessible and serving content
-
Identify the Core Components versionNavigate to the OSGi Bundle Manager at /system/console/bundles and search for 'core.wcm.components.core' or access Package Manager at /crx/packmgr/list.jsp and locate the 'core-wcm-components' package to view the installed version number.Affected if The installed Core Components version is 2.20.6 or earlier
-
Verify the vulnerable component is presentCheck the /apps/core/wcm/components path in CRX/DE (accessible at /crx/de/index.jsp) to confirm the List component or other Core Components that handle URL parameters are installed on the system.Affected if Core Components are installed at the standard path with the vulnerable code present
-
Check for low-author user accountsIn the AEM Users console at /security/users.html or /userdamin, enumerate accounts with 'content-author' or similar low-privilege roles that could be targeted for the reflected XSS attack.Affected if Authenticated users with low author privileges exist in the system
You are affected if Adobe Experience Manager with Core Components version 2.20.6 or earlier is installed and running, as this version contains the reflected XSS vulnerability in the affected component.
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 dataUpdate Adobe Experience Manager Core Components to version 2.20.8 or later to receive the security patch. Additionally, implement URL parameter validation and output encoding as a defense-in-depth measure while planning the update.
- 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-35697 — 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-35697 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