dbcve.org
Experience ManagerApplication · Adobe

CVE-2022-42349

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 · moderate confidence

Reflected Cross-Site Scripting vulnerability in Adobe Experience Manager 6.5.14 and earlier versions. A low-privileged attacker can craft a malicious URL containing JavaScript payloads that get reflected back and executed within the victim's browser when tricked into visiting the link.

MitigationUpgrade to Adobe Experience Manager 6.5.15 or later, or apply the vendor-supplied security patch. Implement URL parameter validation and output encoding on affected endpoints as a 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. Identify Adobe Experience Manager version
    Access the AEM welcome page or check the product info via the system console (:///system/console/bundles or check the jar file properties). For Cloud Service, check the release version in the Cloud Manager or environment details.
    Affected if The installed version is below 6.5.15.0 for AEM on-premise, or below 2022.10.0 for AEM Cloud Service.
  2. Locate accessible AEM endpoints
    Review publicly accessible AEM pages and servlets, particularly those that process URL parameters. Check the Sling servlet registrations and any custom endpoints under /bin, /services, or content paths.
    Affected if Any user-accessible endpoint reflects URL parameters back in the response without proper output encoding.
  3. Test for reflected XSS via URL parameters
    Use a browser or tool like Burp Suite to inject a test payload (such as <script>alert(1)</script> or similar benign XSS probe) into various URL parameters on suspected endpoints and observe if the payload is returned literally in the HTML response.
    Affected if The payload is reflected unencoded or unescaped in the HTTP response, indicating the vulnerability is present.
  4. Verify low-privileged user access
    Attempt to access the suspected vulnerable endpoints using a low-privilege user account (e.g., a read-only user or anonymous access if permitted).
    Affected if Low-privileged or anonymous users can trigger the reflected XSS without authentication.

Your environment is affected if you are running AEM 6.5.14 or earlier on-premise, or a Cloud Service version before 2022.10.0, and any accessible endpoint reflects URL parameters 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

Upgrade to Adobe Experience Manager 6.5.15 or later, or apply the vendor-supplied security patch. Implement URL parameter validation and output encoding on affected endpoints as a defense-in-depth measure.

Recommended fix High confidence

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

  1. 1. Identify your current Adobe Experience Manager version and deployment type (on-prem or Cloud Service)
  2. 2. For on-prem AEM: Schedule an upgrade to version 6.5.15.0 or later following Adobe's upgrade documentation
  3. 3. For AEM Cloud Service: Ensure your environment is updated to the 2022.10.0 release or later
  4. 4. Before deploying to production, test the upgrade in a staging environment to verify compatibility with custom code and configurations
  5. 5. After upgrade, verify the XSS vulnerability is remediated by testing with the previously vulnerable URL patterns
  6. 6. Review Adobe's release notes for 6.5.15.0 for any additional security fixes included in the update
Caveat Review Adobe's upgrade documentation; major version upgrades may require code adjustments and should be tested thoroughly in non-production environments first

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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