dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64581

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows a low-privileged attacker to inject malicious JavaScript into form fields. The payload persists in the system and executes in victim users' browsers when they navigate to pages containing the compromised fields.

MitigationUpdate to AEM 6.5.24 or later; implement strict input validation and output encoding on all form fields; consider Content Security Policy 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. Identify installed AEM version
    Access the AEM welcome page or check the com.adobe.granite.package version via the system console (/system/console/bundles). Compare the version number to the affected ranges: < 6.5.24.0, < 2025.12.0, or exactly 6.5.
    Affected if The installed version is 6.5.23 or earlier, or falls below 2025.12.0, or is exactly 6.5.
  2. Audit form field submissions
    Query the repository (via CRX/DE or oak-run) or export content for form-based pages and look for unexpected script tags, javascript: URIs, or HTML event handlers in text input fields.
    Affected if Any form field contains persisted payloads with script tags, onerror handlers, or javascript: prefixes.
  3. Review user permissions on forms
    Check if low-privilege users (contributors, content authors without admin rights) have access to create or edit form content.
    Affected if Low-privileged users can submit or modify form field values without approval.
  4. Inspect recent content changes
    Review AEM audit logs or version history for form-related content updates from low-privileged users, looking for rapid or bulk submissions.
    Affected if Low-privilege users have recently created or modified form content.

Your AEM instance is affected if it runs version 6.5.23 or earlier (or below 2025.12.0) AND contains form fields where low-privileged users can inject and persist script content.

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

Update to AEM 6.5.24 or later; implement strict input validation and output encoding on all form fields; consider Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

Adobe Experience Manager 6.5.24.0 or later (or migrate to the 2025.12.0 release train)

  1. 1. Review the Adobe Experience Manager 6.5.24.0 release notes for any migration requirements or known issues.
  2. 2. Ensure you have a complete backup of your current AEM instance including the repository, database, and configurations.
  3. 3. Test the upgrade in a non-production environment before deploying to production.
  4. 4. Run the upgrade following Adobe's standard AEM upgrade procedure for your deployment type.
  5. 5. After upgrade, verify that custom form components and user-generated content functionality still work correctly.
  6. 6. Clear all caches and rebuild any search indexes if recommended in the release notes.
Caveat Review upgrade documentation for potential compatibility issues with custom components; minor version upgrades typically have low risk but should be tested

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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