dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64829

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

Adobe Experience Manager 6.5.23 and earlier contains a stored Cross-Site Scripting (XSS) vulnerability. A low-privileged attacker can inject malicious JavaScript into vulnerable form fields, which persists and executes in victim browsers when they view pages containing the compromised fields.

MitigationUpgrade to a patched version of AEM if available; otherwise, implement strict input validation and output encoding on all form fields to prevent script injection.

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 the installed AEM version
    Navigate to AEM Welcome page at /aem/start.html or access the Help menu > About Adobe Experience Manager. Alternatively, check the version.properties file in the crx-quickstart folder or query the /system/console/bundles/org.apache.jackrabbit bundle for version info.
    Affected if The installed version is AEM 6.5.x where x is 23 or lower, or any AEM 2025 version before 2025.12.0.
  2. Verify if AEM Forms is enabled
    Navigate to /aem/forms.html or check the Felix console at /system/console/bundles for 'com.adobe.aemds' bundles in ACTIVE state. Inspect form components in the Touch UI at /editor.html or classic UI dialog configurations.
    Affected if AEM Forms or form-based components are in use and the AEM version is in the affected range.
  3. Inspect form field input validation configuration
    Check the form component Edit dialog XML in /apps or /libs (for example, core form field components under /mnt/override/apps or the granite:FormField node properties). Look at the 'name' and 'value' parameter handling in the validation settings.
    Affected if Form fields lack server-side validation rules or allow raw HTML/JavaScript in input fields.
  4. Check output encoding settings for form submissions
    Review the HTML template used to render form content. Inspect the XSS filter configuration at /etc/clientlibs/foundation/xss or the XSSAPI settings in the Felix console. Verify if form field values are passed through encoding functions before display.
    Affected if Form submissions are rendered back to users without proper HTML encoding (e.g., using context-aware encoding functions).
  5. Search for existing malicious script injections in form data
    Query the AEM repository using CRXDE Lite at /crx/de or the Query tool. Search for form submission nodes under /content/usergenerated or form data stored in repositories containing patterns like '<script' or 'javascript:' in field values.
    Affected if Any stored form entries contain unencoded script tags or event handlers in user input fields.

A user is affected if their AEM installation version is 6.5.23 or earlier (6.5.x series) or any version below 2025.12.0, and the system uses form components that accept and render user input without proper output encoding.

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 a patched version of AEM if available; otherwise, implement strict input validation and output encoding on all form fields to prevent script injection.

Recommended fix High confidence

AEM 6.5.24.0 or later; or AEM 2025.12.0 or later for newer release branches

  1. Verify current Adobe Experience Manager version by accessing /system/console/configMgr or checking the About Adobe Experience Manager page
  2. Download Adobe Experience Manager 6.5.24.0 or later from the Adobe Distribution Portal or official channels
  3. Create a full backup of the AEM instance including the repository, database, and configuration files
  4. Stop the AEM instance before applying the upgrade
  5. Follow Adobe's official upgrade documentation for your specific migration path
  6. Run the upgrade procedure using the Service Pack or Cumulative Fix Pack as appropriate
  7. After upgrade, verify the AEM instance starts successfully and all bundles are in active state
  8. Test the fixed form fields to confirm the XSS vulnerability is remediated
Caveat Review Adobe's compatibility notes before upgrading; some custom components or integrations may require updates for full compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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