dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64558

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

Adobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged authenticated attacker can inject malicious JavaScript payloads into vulnerable form input fields, which persist on the server. When other users browse to pages containing these compromised fields, the malicious script executes in their browsers, potentially stealing session cookies or performing actions on behalf of the victim.

MitigationApply the vendor patch for AEM (version 6.5.24 or later). Until patched, implement output encoding on all form fields and consider disabling or restricting low-privileged user access to form authoring capabilities.

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. Verify AEM version is in affected range
    Access the AEM Web Console ( navigate to /system/console/about ), or check the product.xml file in the installation directory. Compare the installed version to the affected ranges: < 6.5.24.0, < 2025.12.0, or exactly version 6.5.
    Affected if The installed version is lower than 6.5.24.0, lower than 2025.12.0, or is exactly 6.5.x
  2. Confirm low-privileged user access to form authoring exists
    In AEM Tools, navigate to Users/Groups administration and review the permissions assigned to standard content-author or similar low-privileged roles. Check whether these roles have create or modify permissions on form-related content paths (such as /content/forms or /etc/acs-commons).
    Affected if Low-privileged users (non-admin) have permissions to create or edit form fields or form templates
  3. Search repository for suspicious stored payloads in form fields
    Use AEM QueryBuilder or CRX/DE Lite (navigate to /bin/querybuilder.json) to search form-related nodes for common XSS patterns. Query nodes under /content/forms and /apps that contain script tags, javascript:, or on* event handlers in field values.
    Affected if Any form field nodes contain encoded or raw JavaScript payloads, script tags, or event handler attributes that were not authored by administrators

You are affected if your AEM version is below 6.5.24.0 or below 2025.12.0 AND low-privileged users can author or modify form fields, or if malicious scripts already exist in form data stored in the repository.

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 the vendor patch for AEM (version 6.5.24 or later). Until patched, implement output encoding on all form fields and consider disabling or restricting low-privileged user access to form authoring capabilities.

Recommended fix High confidence

AEM 6.5.24.0 or later / AEM as a Cloud Service 2025.12.0 or later

  1. Log into Adobe Admin Console and download Adobe Experience Manager service pack 24 (6.5.24.0) or later
  2. Install the service pack on all AEM author and publish instances following Adobe's standard service pack installation procedure
  3. After installation, verify the AEM version shows 6.5.24.0 or later in the About Adobe Experience Manager information
  4. Clear the AEM dispatcher cache and rebuild to ensure updated assets are served
Caveat Review Adobe Service Pack 24 release notes for any deprecated features or configuration changes before upgrading production environments

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
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,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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