CVE-2025-64873
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 · uneditedAdobe 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 confidenceAdobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privilege attacker can inject malicious JavaScript payloads into vulnerable form fields, which persists in the system and executes in the browsers of users who view the affected pages.
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< 6.5.24.0< 2025.12.0= 6.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed AEM versionAccess the AEM Web Console (System > System Information) or check the version.properties file in the crx-quickstart directory. You can also query the /system/console/bundles.json endpoint or check the 'About Adobe Experience Manager' page in the AEM Welcome screen.Affected if The installed version is less than 6.5.24.0, less than 2025.12.0, or exactly 6.5.x
-
Verify Forms or Adaptive Forms module is in useCheck if the AEM Forms addon is installed by navigating to /libs/fd/fm/view/ or by reviewing installed packages via the Package Manager at /crx/packmgr. Look for forms-related content packages.Affected if Forms functionality is present and accessible to low-privilege users
-
Inspect form field content for malicious scriptsReview content in form containers or Adaptive Form submissions. Use the Query Builder API (for example, query.json with type=dam:Asset or type=nt:unstructured below form paths) to search for common XSS patterns like <script>, javascript:, onerror=, or onload= in form field data.Affected if Form fields contain unsanitized user-supplied content with XSS payloads
-
Review AEM audit logs for XSS exploitation attemptsAccess error.log or audit.log files in crx-quickstart/logs/ and search for unusual patterns in form submission endpoints, particularly around /bin/cq/forms or /services endpoint patterns.Affected if Logs show suspicious form submissions containing XSS vectors
You are affected if your AEM version is below 6.5.24.0 or 2025.12.0 AND you have Forms enabled, with low-privilege users able to submit form content that could contain stored XSS payloads.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.24.02025.12.0
Update Adobe Experience Manager to version 6.5.24 or later. Until the patch is applied, implement output encoding and input validation on affected form fields as a compensating control.
6.5.24.0 (or 2025.12.0/next release for newer cadence)
- Upgrade Adobe Experience Manager to version 6.5.24.0 or later for the 6.5.x release line
- Alternatively, upgrade to version 2025.12.0 or later if using the newer release cadence
- After upgrading, verify that the XSS vulnerability is remediated by testing the affected form fields
- Clear any cached content in AEM to ensure the patched code is served
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64873 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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