CVE-2025-64599
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. Low-privileged attackers can inject malicious JavaScript into vulnerable form fields. When other users view pages containing these compromised fields, the malicious script executes in their browsers.
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/console/bundles) or check the crx-quickstart/package.version file, or use the version prompt in AEM Assets if available. Compare the version number against the affected ranges: versions below 6.5.24.0, below 2025.12.0, or equal to 6.5.Affected if The installed version is 6.5.23 or earlier, or any 6.5.x version below 6.5.24.0, or below 2025.12.0.
-
Identify if AEM Forms is enabledCheck if the AEM Forms addon is installed by navigating to Tools > Forms in the AEM interface, or by reviewing installed packages in the Package Manager for 'aem-forms' or 'forms' packages.Affected if AEM Forms or any form authoring features are active in the environment.
-
Review form field content in the repositoryUse CRXDE Lite (crx/index.jsp) or the Query Builder to search for form component nodes under /content or /apps that contain user-submitted data. Inspect nodes under form field components for unexpected script tags, javascript: URLs, or event handlers.Affected if Malicious script content exists in stored form field data nodes in the repository.
-
Audit low-privilege user accountsCheck the user/group configuration in AEM at Tools > Security > Users or in the Group console. Identify accounts assigned to low-privilege groups that have access to form authoring or content editing.Affected if Low-privileged users have access to create or edit form content that could be exploited.
-
Inspect Content Services or Form Data Model usageIf AEM Forms Data Model or adaptive forms are in use, check the form submission storage locations under /content/forms/af for any suspicious content in submitted data.Affected if Form submission data storage locations contain unescaped user input that could execute.
A user is affected if their AEM version is 6.5.23 or earlier (below 6.5.24.0 or 2025.12.0), AEM Forms features are enabled, and low-privilege users can inject or view form content without proper sanitization.
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
Upgrade Adobe Experience Manager to version 6.5.24 or later to obtain the security patch. Additionally, review and sanitize existing form field content that may contain injected malicious scripts.
AEM 6.5.24.0 or later, or AEM 2025.12.0 or later
- Identify your current Adobe Experience Manager version by checking the AEM welcome page or system console
- Schedule a maintenance window for the upgrade process
- Perform a full backup of your AEM instance including the repository and database
- Create a staging or development environment to test the upgrade before production
- Upgrade AEM to version 6.5.24.0 or later for the 6.5.x release line, or to 2025.12.0 or later for the newer release line
- After upgrade, verify all custom form components are functioning correctly
- Test that the stored XSS vulnerability in form fields is no longer exploitable by attempting to inject malicious scripts
- Deploy the upgraded version to production after successful validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64599 — 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-64599 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