dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64823

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. The malicious payload is stored in the system and executes when users view pages containing the affected fields.

MitigationUpdate Adobe Experience Manager to version 6.5.24 or later to remediate this vulnerability. Additionally, implement input validation, output encoding on form fields, and Content Security Policy (CSP) headers as defense-in-depth measures.

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. Determine Adobe Experience Manager version
    Access the AEM Web Console Bundle information page at /system/console/bundles or check the version.properties file in the crx-quickstart folder. The version is also displayed on the AEM Welcome page at /libs/granite/core/content/login.html
    Affected if The installed version is earlier than 6.5.24.0, earlier than 2025.12.0, or exactly 6.5.x
  2. Verify AEM product edition and release line
    Confirm the AEM installation is the 6.5.x LTS line or the 2025 release train by checking the product name in /system/console/bundles or the crx-quickstart/license.properties file
    Affected if The installation belongs to the 6.5 LTS or 2025 release train and version check from step 1 shows a vulnerable version
  3. Check if author instance is accessible
    Verify whether the AEM author instance is reachable at the standard author port (typically 4502) or the publish instance (typically 4503) by accessing /libs/granite/core/content/login.html
    Affected if The instance is accessible and the version check confirms a vulnerable release - the stored XSS can be exploited by any low-privileged user with form submission access
  4. Identify exposed form components
    Review any custom or out-of-the-box form components in the AEM Forms or Core Components that accept user input and store data in the JCR repository. Check /apps and /libs for form-related components with input fields
    Affected if Form components that accept and store user input exist in the system - combined with a vulnerable version, these fields can accept malicious scripts that persist and execute when viewed

You are affected if your AEM installation runs version 6.5.23 or earlier, version 6.5.x without the .24 update, or any version below 2025.12.0, and you have form components that accept and store user input accessible to low-privileged users.

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 Adobe Experience Manager to version 6.5.24 or later to remediate this vulnerability. Additionally, implement input validation, output encoding on form fields, and Content Security Policy (CSP) headers as defense-in-depth measures.

Recommended fix Moderate confidence

AEM 6.5.24.0+ or AEM 2025.12.0+ (depending on your release line)

  1. Identify your current Adobe Experience Manager version by checking the product information in the AEM welcome page or system console
  2. For AEM 6.5.x versions: Upgrade to AEM 6.5.24.0 or later
  3. For AEM 2025.x versions: Upgrade to 2025.12.0 or later
  4. After upgrading, verify the version in the system console to confirm the patch was applied
  5. Test the affected form fields to ensure the XSS vulnerability is remediated
  6. Review Adobe Experience Manager release notes for the target version for any known issues or migration requirements
Caveat Check Adobe release notes for your specific target version for migration requirements; standard practice is to test in a non-production environment first

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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