dbcve.org
Experience ManagerApplication · Adobe

CVE-2022-42352

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 embed malicious JavaScript into URL parameters targeting vulnerable pages. When a victim is tricked into visiting the crafted URL, the server reflects the unsanitized input back to the browser, executing the attacker's JavaScript within the victim's session context.

MitigationApply the vendor-provided security patch for AEM. Additionally, implement output encoding for user-supplied data in URL parameters and validate all inputs server-side before reflecting them in responses.

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. Identify AEM installation version
    Access the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the crx-quickstart directory. For AEM Cloud Service, check the Cloud Manager environment details or the version info in the developer console.
    Affected if The version displays as lower than 6.5.15.0 for AEM on-premise, or lower than 2022.10.0 for AEM Cloud Service.
  2. Confirm AEM product type
    Determine whether the installation is Adobe Experience Manager on-premise (includes AEM Forms, AEM Sites, AEM Assets) or AEM Cloud Service. This can be verified through the AEM Welcome page or the Cloud Service onboarding interface.
    Affected if The installation is AEM on-premise below version 6.5.15.0 OR AEM Cloud Service below version 2022.10.0.
  3. Inspect URL parameter handling
    Test for reflected XSS by crafting a test URL with a benign script payload in a parameter (for example: ?test=<script>alert(1)</script>). Compare the server response to see if the payload is reflected unsanitized. Only perform this in a non-production or authorized testing environment.
    Affected if The unsanitized script payload appears verbatim in the HTTP response without HTML encoding or sanitization applied by the server.
  4. Check for recent security patches
    Review the installed hotfixes or service packs through the AEM Package Manager at /crx/packmgr, or check the list of installed packages via the System Console at /system/console/bundles to identify if a security patch addressing this CVE has been applied.
    Affected if No security patch for CVE-2022-42352 is installed and the base version falls within the affected ranges.

Your AEM installation is affected if it is AEM on-premise below version 6.5.15.0 or AEM Cloud Service below version 2022.10.0, and URL parameters are reflected in responses without server-side sanitization.

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 vendor-provided security patch for AEM. Additionally, implement output encoding for user-supplied data in URL parameters and validate all inputs server-side before reflecting them in responses.

Recommended fix High confidence

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

  1. For Adobe Experience Manager on-premise: Upgrade to version 6.5.15.0 or later
  2. For Adobe Experience Manager Cloud Service: Ensure the environment is updated to version 2022.10.0 or later
  3. After upgrading, verify the XSS vulnerability is resolved by testing the previously vulnerable endpoints

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42352 — 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-42352 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