Experience ManagerApplication · Adobe

CVE-2022-44473

MEDIUM · 5.4 CVSS v3.1 Published 2022-12-16
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

Reflected XSS vulnerability in Adobe Experience Manager 6.5.14 and earlier allows injection of malicious JavaScript via unsanitized URL parameters. The attack requires social engineering to convince a victim to click a crafted link.

MitigationApply Adobe security patch (upgrade to 6.5.15 or later) and validate that user-supplied input in affected endpoints is properly encoded or sanitized.

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 Adobe Experience Manager version
    Locate the AEM product version through the system console or version file (typically accessible via /system/console or in the product release notes). For Cloud Service, check the deployment version information.
    Affected if The installed version is lower than 6.5.15.0 for AEM on-premise, or lower than 2022.10.0 for AEM Cloud Service.
  2. Verify web-facing accessibility
    Confirm whether the AEM instance is accessible via HTTP/HTTPS from a browser, as reflected XSS requires a user to interact with a crafted URL.
    Affected if The instance is exposed to web users who could potentially click malicious links.
  3. Identify URL parameter handling
    Inspect the application's handling of URL query parameters by reviewing affected endpoint configurations or proxy logs when requests with parameters are submitted.
    Affected if URL parameters are reflected in responses without proper encoding or sanitization.
  4. Check for user input validation
    Review application logs or test common query parameters (such as 'redirect', 'url', or 'path') to observe whether user-supplied values are rendered in HTML responses.
    Affected if Unsantized user input from URL parameters appears directly in the HTTP response.

You are affected if your AEM version is below 6.5.15.0 (on-premise) or below 2022.10.0 (Cloud Service), and your instance handles URL parameters that could be reflected in responses without 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 Adobe security patch (upgrade to 6.5.15 or later) and validate that user-supplied input in affected endpoints is properly encoded or sanitized.

Recommended fix Moderate confidence

Adobe Experience Manager 6.5.15.0+ or Adobe Experience Manager Cloud Service 2022.10.0+

  1. Upgrade Adobe Experience Manager to version 6.5.15.0 or later for the on-premise version
  2. Upgrade Adobe Experience Manager Cloud Service to version 2022.10.0 or later for the cloud version
  3. After upgrading, verify that the reflected XSS vulnerability is no longer present 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-44473 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-44473 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