dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64550

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to 6.5.24.0 / 2025.12.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 versions 6.5.23 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability that could be exploited by a low privileged attacker to execute malicious scripts in the context of the victim's browser. Exploitation of this issue requires user interaction, such as visiting a crafted URL or interacting with a manipulated web page.

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

A DOM-based Cross-Site Scripting vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to inject malicious scripts that execute in the victim's browser context through crafted URLs or manipulated web pages, requiring user interaction to trigger.

MitigationApply Adobe's official security patch for AEM 6.5.23 and earlier versions; until patched, users should avoid clicking untrusted URLs and administrators should implement Content Security Policy headers.

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.24.0< 2025.12.0= 6.5

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 AEM product version
    Access the AEM welcome page or check the version file in the installation directory. On the welcome page, go to Tools > Operations > Diagnosis > Version Info, or look for the version.properties file in the crx-quickstart folder.
    Affected if The displayed version is 6.5.23 or earlier, or falls below 6.5.24.0, or is any version below 2025.12.0 on cloud/ASaaS deployments.
  2. Identify AEM deployment type
    Determine if the instance is AEM on-premise (6.x) or AEM as a Cloud Service / Adobe Managed Services (AMS). Check the welcome page for 'Experience Manager' label or review the installation type in the system console.
    Affected if The instance is AEM 6.5 on-premise (any 6.5.x version) or AEM as a Cloud Service running a version prior to 2025.12.0.
  3. Verify current version against CVE range
    Compare your installed version number to the affected ranges: AEM 6.5 versions below 6.5.24.0, or AEM Cloud/AMS versions below 2025.12.0. Note the exact version displayed in the version info.
    Affected if Your version is 6.5.23, 6.5.22, 6.5.21, or any earlier 6.5.x release; or your cloud version is any build prior to the 2025.12.0 release.
  4. Review recent security incidents
    Check server logs and browser console for any reports of suspicious script execution, unexpected JavaScript loading, or user complaints about injected alerts/popups originating from AEM-hosted pages.
    Affected if Any evidence of arbitrary script execution in user browsers indicates the vulnerability may have been exploited.

You are affected if your AEM installation is version 6.5.23 or earlier on-premise, or any version below 2025.12.0 on AEM Cloud/Managed Services.

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.24.0 / 2025.12.0 or later
Fixed in 6.5.24.02025.12.0
Interim mitigation

Apply Adobe's official security patch for AEM 6.5.23 and earlier versions; until patched, users should avoid clicking untrusted URLs and administrators should implement Content Security Policy headers.

Recommended fix High confidence

AEM 6.5.x -> 6.5.24.0 or later; AEM Cloud/2025.x -> 2025.12.0 or later

  1. 1. Identify the current Adobe Experience Manager version in use by checking the product About page or system console
  2. 2. For AEM 6.5.x installations: Plan an upgrade to version 6.5.24.0 or later
  3. 3. For AEM as a Cloud Service or 2025 release line: Plan an upgrade to version 2025.12.0 or later
  4. 4. Test the upgrade in a non-production environment before deploying to production
  5. 5. After upgrading, verify the fix by checking the AEM version information
  6. 6. Monitor Adobe Security Bulletins for any subsequent updates
Caveat Standard AEM upgrade considerations apply - review compatibility, test custom code, and ensure third-party integrations work with the target version

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-2025-64550 — 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-2025-64550 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