CVE-2025-64841
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 vulnerability where low-privileged users can inject malicious JavaScript into form fields. When other users browse to 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.
-
Confirm Adobe Experience Manager is installedCheck for AEM by looking for the typical installation directory (e.g., /opt/aem, /crx, or C:\AEM) or check running processes for 'aem' or 'cq' in the process nameAffected if AEM software is not present on the system, this CVE does not apply
-
Identify installed AEM versionNavigate to the AEM Welcome page and access 'Version' under 'Tools > Operations' or check the manifest file in the AEM installation directory (e.g., quickstart/org.apache.jackrabbit-standaloneVERSION file)Affected if The installed version is less than 6.5.24.0, less than 2025.12.0, or exactly 6.5 (any 6.5.x version below 6.5.24.0)
-
Determine if AEM Forms module is enabledCheck if the Forms functionality is installed by navigating to 'Tools > Forms' in the AEM author instance, or check the package manager for 'aem-forms' packagesAffected if Forms module is installed and enabled - the vulnerability affects form field inputs specifically
-
Verify low-privileged user access to form authoringReview user/group permissions in AEM User Management (Tools > Security > Users or Groups) and check if standard authors or contributors have access to create or edit Adaptive Forms or Form FragmentsAffected if Low-privilege users (contributors, authors) have permissions to create or edit form content without requiring approval
-
Confirm exposed form endpoints accessible to usersCheck the public-facing publish instances for Adaptive Forms or Form containers at /content/forms/af/ or similar paths, and verify if unauthenticated or low-privileged users can access form rendering pagesAffected if Forms with user-supplied input fields are exposed to other users who would browse and trigger the stored XSS
You are affected if AEM is installed with version below 6.5.24.0 or below 2025.12.0, the Forms module is enabled, and low-privileged users can inject content into form fields that are rendered to other users.
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
Apply the vendor patch for AEM 6.5.24 or later. Until patched, implement input validation/sanitization on form fields and output encoding when rendering user-supplied content.
Adobe Experience Manager 6.5.24.0
- 1. Check the current Adobe Experience Manager version by navigating to the AEM Welcome page and checking the version information
- 2. Back up the AEM instance including the repository, configuration, and any custom code before upgrading
- 3. Review Adobe Experience Manager 6.5.24.0 release notes for any breaking changes, migration requirements, or compatibility notes
- 4. Upgrade Adobe Experience Manager to version 6.5.24.0 or later following Adobe's standard upgrade procedures
- 5. After upgrading, verify the XSS vulnerability is patched by testing form fields that could be used for injection
- 6. Validate that existing custom components, workflows, and integrations function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64841 — 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-64841 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