dbcve.org
Experience ManagerApplication · Adobe

CVE-2022-42364

MEDIUM · 5.4 CVSS v3.1 Published 2022-12-19
Fix available
A fix is available. Upgrade to 6.5.15.0 / 2022.10.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Adobe 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 confidence

Adobe Experience Manager versions 6.5.14 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability. An attacker can inject malicious JavaScript into a URL parameter that gets reflected back to the victim's browser without proper sanitization. Successful exploitation requires tricking a user into visiting a specially crafted URL.

MitigationApply the appropriate Adobe security patch for AEM 6.5.14 or upgrade to a fixed version. Additionally, implement input validation and output encoding on the affected endpoint to prevent reflected XSS.

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
Experience ManagerApplication
Affected:< 6.5.15.0
Experience Manager Cloud ServiceApplication
Affected:< 2022.10.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed AEM version
    Access the AEM welcome page or check the version file in the crx-quickstart folder. On the welcome page, look for the version number displayed. Alternatively, check the manifest file in the install folder or use the Version Info MBean via the Felix console.
    Affected if The installed version is AEM 6.5.14.0 or earlier, or for Cloud Service, the version is before 2022.10.0
  2. Identify AEM Cloud Service version
    If using AEM Cloud Service, check the Cloud Manager UI or the release notes for the current deployment version number.
    Affected if The Cloud Service version is before 2022.10.0
  3. Review deployed custom code for URL parameter handling
    Examine any custom OSGi bundles, servlets, or JSP/HTL components that process URL query parameters and return them in responses. Look for code that uses request.getParameter() and outputs the value without encoding.
    Affected if Custom code reflects URL parameter values directly into HTTP responses without proper output encoding or input validation
  4. Audit publicly accessible endpoints
    Identify all publicly accessible endpoints and their parameter handling. Test by passing a benign test string (like 'test<script>alert(1)</script>') in various URL parameters and checking if the script tags appear unencoded in the response.
    Affected if Any endpoint reflects URL parameter input back into the response body without HTML encoding

You are affected if your AEM deployment is version 6.5.14.0 or earlier for on-premise, or version before 2022.10.0 for Cloud Service, AND any publicly accessible endpoint reflects URL parameter input without proper output encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.15.0 / 2022.10.0 or later
Fixed in 6.5.15.02022.10.0
Interim mitigation

Apply the appropriate Adobe security patch for AEM 6.5.14 or upgrade to a fixed version. Additionally, implement input validation and output encoding on the affected endpoint to prevent reflected XSS.

Recommended fix High confidence

AEM 6.5.15.0+ (on-premise) or AEM Cloud Service 2022.10.0+

  1. 1. Back up your current AEM instance and content repository before proceeding with any upgrade
  2. 2. Review the Adobe Experience Manager 6.5.15 release notes at helpx.adobe.com for full details on changes and potential compatibility considerations
  3. 3. For AEM on-premise installations: Upgrade Adobe Experience Manager to version 6.5.15.0 or later
  4. 4. For AEM Cloud Service: Ensure your environment is updated to the 2022.10.0 release or later
  5. 5. After upgrade, verify that the Reflected XSS vulnerability is resolved by testing the previously vulnerable URL patterns
  6. 6. Clear browser caches and test that AEM functionality remains intact post-upgrade
Caveat Review AEM 6.5.15 release notes for any compatibility changes; test thoroughly in non-production environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42364 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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