Experience ManagerApplication · Adobe

CVE-2022-35694

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. Attack requires social engineering to convince victims to click a malicious URL containing unsanitized JavaScript that executes within the victim's browser context.

MitigationApply the vendor security patch from Adobe. Users should avoid clicking untrusted URLs referencing AEM pages.

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 AEM 6.5.x version
    Access the AEM System Information console at /system/console/bundles or /libs/granite/core/content/login.html to view the installed product version. Alternatively, check the crx-quickstart/license.properties file for the product version string.
    Affected if The displayed version is 6.5.14.0 or earlier (less than 6.5.15.0)
  2. Determine AEM Cloud Service version
    Check the Cloud Service release version through the Adobe Cloud Manager console or the system information available at /system/console/bundles in the AEM Cloud environment.
    Affected if The Cloud Service version is earlier than 2022.10.0 (the October 2022 release)
  3. Verify the affected deployment
    Confirm whether your AEM instance is exposed to the web and accessible via HTTP/HTTPS URLs that users might click. Check if the instance has external-facing publish or preview instances.
    Affected if The instance is internet-facing and users could potentially click crafted URLs pointing to AEM pages

You are affected if your AEM 6.5.x installation is version 6.5.14.0 or earlier, or your AEM Cloud Service is before the October 2022 (2022.10.0) release, and the instance is accessible for users to click malicious URLs.

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 security patch from Adobe. Users should avoid clicking untrusted URLs referencing AEM pages.

Recommended fix High confidence

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

  1. Identify your current Adobe Experience Manager version (6.5.x on-premises or Cloud Service)
  2. For AEM 6.5.x on-premises: Upgrade to version 6.5.15.0 or later
  3. For AEM Cloud Service: Ensure your environment is updated to version 2022.10.0 or later
  4. After upgrading, verify that the reflected XSS vulnerability is resolved by testing with crafted URLs in a non-production environment
  5. Confirm the fix by reviewing the Adobe security bulletin for CVE-2022-35694
Caveat Standard AEM upgrade precautions apply - review Adobe's upgrade documentation for your specific version jump, test thoroughly in non-production, and backup your environment before upgrading

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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