CVE-2022-42362
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 XSS vulnerability where user-supplied input in URL parameters is insufficiently sanitized, allowing malicious JavaScript to execute in victim's browser when tricked into visiting a crafted URL.
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 version from system consoleNavigate to the AEM system console at /system/console/systeminfo or access Help > About Adobe Experience Manager to view the installed version numberAffected if The displayed version is 6.5.14.x or earlier, or the version starts with 6.5.14.x (for AEM 6.5.x releases)
-
Check AEM Cloud Service versionAccess the Cloud Manager environment details or the AEM Author console, then locate the version information typically shown in the system console or support utilityAffected if The Cloud Service version is earlier than 2022.10.0 (for example, 2022.08.0 or earlier)
-
Confirm AEM 6.5.x baseline versionIf running AEM 6.5 on-premises, check the version.properties file in the crx-quickstart folder or the manifest.mf file within the AEM quickstart JAR to confirm the exact 6.5.x release numberAffected if The version is 6.5.14.0 or any 6.5.x version below 6.5.15.0
-
Identify exposed URL parametersReview application logs and access the AEM Debugger or request logs to identify URL parameter usage patterns, particularly those that accept user input and might be reflected in the responseAffected if The application uses URL parameters that accept unsanitized user input and return that input in the HTTP response without proper encoding
You are affected if your installed Adobe Experience Manager version is below 6.5.15.0 (for 6.5.x releases) or below 2022.10.0 (for Cloud Service), as these are the only versions containing the unpatched reflected XSS vulnerability.
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's security patch for AEM 6.5.14 or upgrade to a patched version. Validate and encode all user inputs in URL parameters before rendering.
AEM 6.5.15.0 (on-premise) or 2022.10.0 (Cloud Service)
- For Adobe Experience Manager on-premise: Upgrade to version 6.5.15.0 or later
- For Adobe Experience Manager Cloud Service: Upgrade to version 2022.10.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42362 — 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-42362 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