CVE-2025-64572
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 · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager where low-privileged users can inject malicious JavaScript into form fields. The malicious script persists and executes in victim browsers when they navigate to pages containing the affected fields.
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.
-
Identify Adobe Experience Manager installation and versionCheck the AEM version by accessing the system information console at /system/console/bundles or by reviewing the pom.xml/cq-quickstart product.xml file in the AEM installation directory. Also check the About Adobe Experience Manager page accessible from the AEM start menu.Affected if The installed version is less than 6.5.24.0, less than 2025.12.0, or within the 6.5.x line (6.5.0.0 through 6.5.23.x).
-
Verify presence of form components or custom form fieldsReview the AEM instance for any Form components, Adaptive Forms, or custom form field implementations in the /content directory. Use CRX/DE to navigate to /apps and /content and search for form-related components.Affected if Form components or editable form fields exist in the AEM instance and the version is within the affected range.
-
Confirm low-privileged user access to form editingReview user and group permissions in AEM User Management (/security/users.html or /libs/cq/security/content/admin.html). Check if standard users or members of groups like 'content-authors' have create or modify permissions on form-related content nodes.Affected if Low-privileged users (non-administrators) have write access to form content or form components.
-
Check for existing injected scripts in form contentUse CRX/DE or the Query Builder API to search for stored script tags in form-related content nodes. Query /content for patterns like '<script' or 'javascript:' in text fields. Example Query Builder query: path=/content, type=sling:OrderedFolder, property=jcr:content/*, property.value=%3Cscript%25Affected if Malicious script tags are found stored within form field content nodes in the repository.
A user is affected if they are running Adobe Experience Manager version 6.5.x prior to 6.5.24.0 or version 2025.x prior to 2025.12.0, and the instance has accessible form components that allow low-privileged users to input or modify content.
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 a version newer than 6.5.23. As an interim measure, implement strict input validation and output encoding on all form fields to prevent script injection.
AEM 6.5.24.0 or later; AEM as a Cloud Service 2025.12.0 or later
- Backup the current AEM instance and content repository before proceeding with any upgrade
- Review Adobe's official upgrade documentation for AEM 6.5.24.0 or AEM as a Cloud Service 2025.12.0
- Ensure the target environment meets the minimum system requirements for the fixed version
- Test the upgrade in a non-production environment first to verify compatibility with custom code and configurations
- Apply the upgrade to AEM 6.5.24.0 or later (for on-premise) or deploy to AEM as a Cloud Service 2025.12.0 or later
- Verify the upgrade was successful and test that the XSS vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2025-64572 — 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-64572 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