CVE-2025-64822
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 into vulnerable form inputs, which persists in the system and executes when other users view 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.
-
Determine Adobe Experience Manager versionCheck the product version via the AEM welcome page (/aem/start.html), the system console (/system/console/bundles), or by inspecting the manifest file in the AEM installation directory. Common locations: crx-quickstart/app/org.apache.sling.launchpad-*.jar or the version.properties file.Affected if The installed version is below 6.5.24.0, equals 6.5, or is below 2025.12.0 (for the 2025 release branch)
-
Identify form components in useReview the AEM instance for deployed form components. Check the following paths in the CRX/DE repository under /apps or /libs: /libs/foundation/components/form, /libs/wcm/foundation/components/form, or custom form components under /apps. You can also search for components with 'form' in the name using the AEM query builder or CRX search.Affected if Form components are present and users can submit input through them
-
Verify input sanitization configurationExamine the form field component configurations in the CRX/DE repository. Check the JSP, HTL, or Granite UI form components under /libs/foundation/components/form/* for any server-side validation or sanitization logic. Look for the presence of XSS protection libraries or encoding functions in the form submission handlers.Affected if No server-side input sanitization is found on form field components or the sanitization logic can be bypassed
-
Confirm user permission levelsReview which user groups have access to create or edit form content. Check the ACLs (Access Control Lists) in AEM under /useradmin or in the CRX repository under /home/groups and /home/users. Specifically verify if low-privilege users (contributors, content authors) can access form components.Affected if Low-privilege users have write access to form fields or form content
If the AEM version is 6.5.x before 6.5.24.0, 6.5, or any version below 2025.12.0 AND the system uses form components that accept user input, the environment is likely affected by this stored XSS vulnerability.
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. After upgrading, verify that user-supplied input in form fields is properly sanitized.
Adobe Experience Manager 6.5.24.0 or later (or 2025.12.0 and later)
- Back up the current Adobe Experience Manager instance and all content repositories
- Download Adobe Experience Manager 6.5.24.0 or later from the official Adobe distribution portal
- Review Adobe's official upgrade documentation for 6.5.x to 6.5.24.0 migration requirements
- Execute the upgrade following Adobe's recommended upgrade procedure
- After upgrade, verify that the XSS vulnerability in form fields is patched by testing with a benign script payload
- Confirm all custom code and third-party integrations remain functional post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64822 — 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-64822 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