dbcve.org
Experience ManagerApplication · Adobe

CVE-2022-35693

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 Cross-Site Scripting (XSS) vulnerability. The attack requires a low-privileged attacker to socially engineer a victim into visiting a specially crafted URL containing malicious JavaScript, which then executes within the victim's browser context.

MitigationApply the vendor patch for AEM 6.5.14 or later versions. Alternatively, implement input validation and output encoding on the vulnerable parameter to neutralize script injection.

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 the installed AEM version
    Access the AEM Welcome page or use the version information endpoint (e.g., /system/console/status-productinfo or check the jar manifest). Alternatively, check the crx-quickstart/etc/version.txt file or the package manager for the core AEM version.
    Affected if The installed version is Adobe Experience Manager 6.5.14 or earlier, or Adobe Experience Manager Cloud Service version earlier than 2022.10.0
  2. Confirm AEM Cloud Service deployment version
    If using AEM Cloud Service, check the Cloud Manager pipeline execution history or the environment details in the Cloud Manager console to identify the release version number.
    Affected if The Cloud Service version is earlier than 2022.10.0
  3. Audit the application for reflected XSS vulnerabilities
    Review web application firewall (WAF) logs, penetration testing reports, or use a web vulnerability scanner to identify any reflected XSS patterns in HTTP responses.
    Affected if Reflected parameters in URLs are found to return unencoded user input back in the HTTP response without proper sanitization
  4. Inspect custom code for input validation gaps
    Examine the codebase for custom sling selectors, servlets, or JSP/HTL files that handle URL parameters. Search for request.getParameter calls where the output is written directly to the response without encoding.
    Affected if Custom code handles URL parameters and writes them to the response without input validation or output encoding

You are affected if your AEM deployment is version 6.5.14 or earlier for the on-premise variant, or earlier than 2022.10.0 for Cloud Service, and the vulnerable reflected XSS endpoint is accessible to low-privileged users.

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 patch for AEM 6.5.14 or later versions. Alternatively, implement input validation and output encoding on the vulnerable parameter to neutralize script injection.

Recommended fix High confidence

AEM 6.5.15.0 (on-premises) or AEM Cloud Service version 2022.10.0+

  1. 1. Review the Adobe Experience Manager 6.5.15 release notes at helpx.adobe.com for upgrade requirements and known issues
  2. 2. Create a full backup of your AEM instance and content repository before upgrading
  3. 3. Download Adobe Experience Manager version 6.5.15.0 or later from the Adobe distribution portal
  4. 4. Stop the AEM instance
  5. 5. Run the upgrade installer following Adobe's standard upgrade procedure
  6. 6. Start the AEM instance after upgrade completes
  7. 7. Verify that the XSS vulnerability is resolved by testing the affected URL patterns
  8. 8. For AEM Cloud Service customers, ensure deployment occurs with version 2022.10.0 or later via Cloud Manager
Caveat Review Adobe's 6.5.15 release notes for potential compatibility issues with custom code or third-party integrations; some deprecated APIs may require updates

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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