CVE-2022-42348
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 6.5.14 and earlier contains a reflected Cross-Site Scripting (XSS) vulnerability. A low-privileged attacker can craft a malicious URL containing JavaScript payload that, when clicked by a victim, executes within the context of the victim's browser due to insufficient input sanitization or output encoding on the vulnerable page.
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.
-
Determine your AEM deployment typeIdentify whether you are running Adobe Experience Manager 6.5.x (on-premise) or Adobe Experience Manager Cloud Service, as the version checking method differs by deploymentAffected if The deployment type is AEM 6.5.x or AEM Cloud Service
-
Check AEM 6.5.x versionAccess the AEM welcome page or system information console and locate the Product Version field to identify the installed 6.5.x version numberAffected if The installed version is 6.5.14.0 or earlier (any version < 6.5.15.0)
-
Check AEM Cloud Service versionAccess the Cloud Service version information through the Cloud Manager interface or the system console and locate the deployed version identifierAffected if The installed version is any version released before 2022.10.0
-
Confirm XSS exposure existsSince this is a reflected XSS, verify that user-supplied parameters can be passed to vulnerable endpoints without sanitization - the vulnerability exists in the version check alone as the flaw is in input handling across the affected pagesAffected if You are on a version that falls within the vulnerable ranges regardless of specific endpoint configuration
You are affected if your AEM 6.5.x installation is version 6.5.14.0 or earlier, or your AEM Cloud Service version is before the 2022.10.0 release.
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 6.5.15 or later. Alternatively, implement proper input validation and output encoding on affected endpoints, and deploy Content Security Policy (CSP) headers to mitigate XSS attacks.
Adobe Experience Manager 6.5.15.0 (on-premise) or 2022.10.0 (Cloud Service)
- 1. Identify the current Adobe Experience Manager version in use (on-premise or Cloud Service)
- 2. For AEM on-premise: Upgrade to version 6.5.15.0 or later
- 3. For AEM Cloud Service: Upgrade to version 2022.10.0 or later
- 4. After upgrade, verify the new version is running
- 5. Test that the reflected XSS vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42348 — 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-42348 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