CVE-2025-64547
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 confidenceAdobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where low-privileged attackers can inject malicious JavaScript into vulnerable form fields. The malicious payload persists in the system and executes in victim users' 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.
-
Check installed AEM versionNavigate to AEM Welcome page (typically at /aem/start.html) or access the system information via Help > About Adobe Experience Manager in the AEM console. Alternatively, query the version through the OSGi bundle console at /system/console/bundles or via the CRXDE Lite interface at /crx/de. Compare the displayed version number against the affected ranges: versions below 6.5.24.0, version 6.5.x, or releases below 2025.12.0.Affected if The installed version is 6.5.x, 6.5.23 or earlier, or any version below 2025.12.0, matching the vulnerable release ranges.
-
Identify deployed form componentsReview the AEM instance for use of Adaptive Form components, Core Form components, or Foundation Form components. Access the AEM Sites console and examine any content pages that contain form containers or form fields. Use the Template Editor or the Content Finder to locate form structures under /content or /apps directories.Affected if Form components (particularly Adaptive Forms, Core Components Forms, or Foundation Forms) are deployed and accessible on the AEM instance.
-
Inspect stored form data for malicious payloadsAccess the AEM repository via CRXDE Lite at /crx/de or use the Query Builder to search for persisted form submission data. Examine nodes under /content/forms/af or similar form data storage paths. Look for script tags, javascript: URIs, event handlers (onerror, onload, onclick), or encoded suspicious patterns in stored field values.Affected if Form submission data exists in the repository containing XSS payloads such as <script>, javascript:, or HTML event handler attributes.
-
Verify form field output encoding settingsLocate the form field component definitions in the AEM component console or within the /apps directory structure. Check the component's JSP, HTL, or Granite UI form field configurations for presence of proper output encoding mechanisms such as context-aware encoding (using encoding APIs like xssAPI or equivalent). Examine whether input validation rules are configured for the form fields.Affected if Form field components lack output encoding or input validation controls, leaving user-supplied data rendered without sanitization.
-
Review form submission workflow configurationAccess the AEM Workflow console at /libs/cq/workflow/content/console.html or the Form Workflow settings. Examine whether form submissions are processed through a workflow that includes XSS protection steps or whether data is stored directly without sanitization. Check the dataStore or Granite UI form data persistence configuration.Affected if Form submissions bypass XSS sanitization workflows or store user input in raw form without encoding validation.
An AEM instance is affected if it runs version 6.5.23 or earlier (or below 2025.12.0), has form components deployed, and contains unsanitized user input stored in form fields that could be rendered without proper encoding.
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 Adobe's official patch by updating to AEM version 6.5.24 or later; additionally, implement output encoding and input validation on vulnerable form fields to prevent XSS attacks.
AEM 6.5.24.0 or later; or AEM 2025.12.0 or later
- 1. Review the Adobe Experience Manager release notes for version 6.5.24.0 or 2025.12.0 to understand changes and any migration requirements
- 2. Perform a full backup of the AEM instance including repository, database, and configuration files
- 3. Test the upgrade in a non-production environment before deploying to production
- 4. Apply the upgrade to AEM 6.5.24.0 or later (for 6.5.x line) or to 2025.12.0 or later (for newer release train)
- 5. Verify that the upgraded form fields no longer accept malicious script injections
- 6. Test critical user workflows to ensure functionality is intact
- 7. Deploy the tested upgrade to production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64547 — 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-64547 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