dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64627

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 stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. When victims browse pages containing these compromised fields, the script executes in their browsers, potentially enabling session hijacking or data theft.

MitigationUpgrade to AEM 6.5.24 or later. Implement strict input validation and output encoding on all form fields, and deploy Content Security Policy (CSP) headers to mitigate XSS execution.

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 version via Help menu
    Log into AEM as administrator, click the Adobe Experience Manager icon (top-left), select Help > About Adobe Experience Manager, and note the version number displayed
    Affected if The displayed version is 6.5.23 or earlier, equals 6.5, or is less than 2025.12.0
  2. Check AEM version via version.properties
    Locate the version.properties or version.info file in the crx-quickstart directory of your AEM installation and read the ProductVersion or version field
    Affected if The version file shows a version lower than 6.5.24.0 or lower than 2025.12.0, or shows exactly 6.5 without a patch number
  3. Check version via Web Console
    Access the AEM Web Console at /system/console/bundles and locate the Adobe Experience Manager Core Bundle (or similar core bundle), then view its version information
    Affected if The bundle version indicates an AEM release prior to 6.5.24.0 or prior to the 2025.12.0 release

You are affected if your installed AEM version is 6.5.23 or earlier, equals 6.5 without a specific patch version, or is earlier than the 2025.12.0 release.

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

Upgrade to AEM 6.5.24 or later. Implement strict input validation and output encoding on all form fields, and deploy Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix Moderate confidence

AEM 6.5.24.0 (minimum) or AEM 2025.12.0 for newer releases

  1. 1. Identify the current Adobe Experience Manager version in use (check /system/console/bundles or the About AEM page)
  2. 2. For AEM 6.5.x line: Upgrade to AEM 6.5.24.0 or later
  3. 3. For newer release line: Upgrade to 2025.12.0 or later
  4. 4. After upgrade, verify the Forms component patches are applied by checking the AEM Forms add-on package version
  5. 5. Test the fix by attempting to submit a script payload in form fields that previously allowed XSS
  6. 6. Clear AEM caches and publish instances to ensure the fixed code is deployed

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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