dbcve.org
Experience ManagerApplication · Adobe

CVE-2022-44470

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 6.5.14 and earlier contains a reflected XSS vulnerability where user-supplied input in a URL parameter is rendered back to the user without proper output encoding, allowing execution of arbitrary JavaScript in the victim's browser context.

MitigationApply proper output encoding or use AEM's built-in XSS protection APIs to sanitize user input before reflecting it in the response. Consider implementing a Content Security Policy (CSP) header as an additional defense-in-depth measure.

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. Check Adobe Experience Manager version
    Access the AEM System Information console at /system/console/product, or inspect the quickstart JAR file manifest for the Bundle-Version entry
    Affected if The displayed version is below 6.5.15.0 for AEM on-premise installations
  2. Check AEM Cloud Service version
    Navigate to the Cloud Manager environment details or check the AEM version via the Developer Console at /libs/granite/ops/transparentconsole
    Affected if The version is earlier than 2022.10.0 for AEM Cloud Service instances
  3. Identify reflected parameters in URLs
    Review application error handlers and custom error pages that render URL parameters back to users without encoding, test by appending a benign string like <script>alert(1)</script> to suspected URL parameters and observing if it is reflected as-is in the response
    Affected if URL parameter values are returned in the HTTP response without HTML encoding, allowing the injected script to execute in the browser context

Your environment is affected if you are running Adobe Experience Manager on-premise below version 6.5.15.0 or AEM Cloud Service below version 2022.10.0, and your application reflects URL parameter input back to users 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 proper output encoding or use AEM's built-in XSS protection APIs to sanitize user input before reflecting it in the response. Consider implementing a Content Security Policy (CSP) header as an additional defense-in-depth measure.

Recommended fix High confidence

Adobe Experience Manager 6.5.15.0 (on-premise) / Adobe Experience Manager Cloud Service 2022.10.0

  1. For Adobe Experience Manager (AEM) 6.5 on-premise: Upgrade the AEM instance to version 6.5.15.0 or later to address the reflected XSS vulnerability
  2. For Adobe Experience Manager Cloud Service: Ensure the environment is updated to version 2022.10.0 or later via the Cloud Manager auto-upgrade feature or by requesting an upgrade
  3. After upgrading, verify that the XSS vulnerability is resolved by testing the previously vulnerable endpoints
  4. Review the AEM 6.5.15 release notes for any additional security fixes included in the update
Caveat Review AEM 6.5.15 release notes for compatibility notes; test custom code and integrations in a staging environment before production deployment

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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