CVE-2022-42367
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 confidenceReflected XSS vulnerability in Adobe Experience Manager 6.5.14 and earlier allows low-privilege attackers to inject malicious JavaScript via specially crafted URLs. When victims click attacker-controlled links, the malicious script executes within their browser context, potentially stealing session tokens or performing actions on behalf of the user.
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 6.5 version numberAccess the AEM system console or welcome page (typically at /libs/granite/core/content/login.html or check the footer of the AEM start page). The version is also available via the OSGi bundle information at /system/console/status-productinfoAffected if Version displayed is below 6.5.15.0 (for example, 6.5.14.0 or earlier)
-
Check AEM Cloud Service release versionCheck the Cloud Service version through the AEM admin console, release notes, or the version information available in the Cloud Manager interfaceAffected if Running a release version earlier than 2022.10.0
-
Verify low-privilege user access existsReview user and group permissions in the AEM user admin console at /security/users.html or /security/groups.html to confirm low-privilege accounts (such as 'users' group members) can access the systemAffected if Low-privilege users can log in or access vulnerable endpoints
-
Confirm web interface accessibilityCheck if the AEM publish or author instance web interfaces are reachable from untrusted networks, or review dispatcher/firewall rules to determine which endpoints are externally accessibleAffected if Web interfaces or specific endpoints are accessible to unauthenticated or low-privilege attackers who could deliver malicious URLs
The environment is affected if running AEM 6.5 version below 6.5.15.0 or AEM Cloud Service before 2022.10.0, AND low-privilege users or attackers can access web endpoints that process 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
Apply Adobe security patch for AEM 6.5.15 or later to address this vulnerability. As defense-in-depth, implement URL input validation and output encoding on affected endpoints.
Experience Manager 6.5.15.0 (on-premise) or 2022.10.0 (Cloud Service)
- Verify current Adobe Experience Manager version in use (on-premise or Cloud Service)
- For Experience Manager on-premise: Plan upgrade to version 6.5.15.0 or later
- For Experience Manager Cloud Service: Plan upgrade to version 2022.10.0 or later
- Review Adobe's upgrade documentation and release notes for the target version
- Schedule maintenance window for upgrade procedure
- Execute upgrade following Adobe's standard upgrade process
- Validate the upgrade was successful and the application is functioning correctly
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-42367 — 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-42367 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