CVE-2025-64825
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager forms. A low-privilege attacker can inject malicious JavaScript into form fields, which persists in the system and executes in victim browsers when they view 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.
-
Identify the Adobe Experience Manager versionAccess the AEM Web Console (Help > System Information) or check the version.properties file in the crx-quickstart folder. Alternatively, append /system/console/configMgr to your AEM URL and look for version information.Affected if The installed version is 6.5 (any variant), below 6.5.24.0, or below 2025.12.0. Any of these versions fall within the affected range.
-
Verify if AEM Forms is installed and activeCheck the AEM Package Manager (/crx/packmgr) for installed form-related packages, or navigate to Forms in the AEM navigation panel. Look for the presence of 'cq-msm-form' or similar form packages.Affected if The Forms module is installed and enabled in the AEM instance.
-
Determine if low-privilege users have form authoring accessReview the group permissions in AEM (Tools > Security > Groups). Check if non-admin groups like 'forms-users' or 'content-authors' have permission to create or edit Adaptive Forms.Affected if Users with low-privilege roles (content-author, forms-user, or similar) can create or modify form fields.
-
Inspect stored form data for existing submissionsUse CRXDE Lite (/crx/de) or the AEM Form Manager to browse form submission data. Navigate to /content/forms/af or similar form storage paths in the repository.Affected if There are existing form submissions stored in the repository, particularly from untrusted sources.
-
Check form field input validation configurationReview the Adaptive Form configuration in AEM Forms (select a form > Edit > Open rule editor or field properties). Inspect whether input validation and output encoding are configured.Affected if Form fields lack input validation rules or output encoding settings, allowing arbitrary script injection.
Your environment is affected if you are running any AEM version in the 6.5 family or versions below 6.5.24.0/2025.12.0, AND the AEM Forms module is enabled with form submissions present or low-privilege users able to create forms.
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. Additionally, audit existing form submissions for malicious payload injection and implement output encoding for all user-supplied data displayed in form fields.
6.5.24.0 or later (6.5 branch); 2025.12.0 or later (cloud release)
- 1. Back up the current Adobe Experience Manager instance, including repository content and configurations
- 2. Create a staging or development environment mirroring production
- 3. Download Adobe Experience Manager 6.5.24.0 (for 6.5 branch) or 2025.12.0 (for cloud release) from the official Adobe distribution portal
- 4. Install the upgrade package in the staging environment and verify all custom workflows, integrations, and form components function correctly
- 5. After testing, apply the upgrade to production during a scheduled maintenance window
- 6. Clear AEM repository caches and rebuild any search indexes post-upgrade
- 7. Verify the XSS vulnerability is remediated by attempting to inject script content into affected form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64825 — 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-64825 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