CVE-2025-64549
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 versions 6.5.23 and earlier allows low-privileged attackers to inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing the compromised fields, the injected 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.
-
Check your Adobe Experience Manager versionNavigate to the AEM welcome page and click 'About Adobe Experience Manager', or access /system/console/configMgr and look for com.adobe.granite.commons.version. Compare the displayed version against the affected ranges: versions before 6.5.24.0, before 2025.12.0, or any 6.5.x release are vulnerable.Affected if The installed version is below 6.5.24.0, below 2025.12.0, or is any 6.5.x release.
-
Identify form components accepting user inputReview your AEM instance for Adaptive Forms, Core Components forms, or custom form implementations. Check the CRX/DE repository under /apps or /content for form field components (look for nodes with 'form' in the resource type or component group).Affected if Form components exist that accept user-submitted data without validation.
-
Verify if low-privileged users have form submission permissionsNavigate to AEM Tools > Security > Permissions, or check the user/group permissions under /home/users. Verify if users with 'content-author' or similar low-privilege roles can access and submit form content.Affected if Low-privileged users (non-admin) have write or submit access to form fields.
-
Inspect form field input validation settingsIn AEM Forms or Core Components edit dialogs for form fields, check the Validation tab or field properties. Look for 'Validation Type' settings and whether server-side validation or XSS protection is configured.Affected if Form fields lack input validation configuration or XSS protection rules.
-
Search for existing malicious scripts in form dataQuery the AEM repository or form submission storage (JCR nodes under /content/forms or custom data stores) for common XSS payloads: <script>, javascript:, onerror=, onload=, or encoded variants.Affected if Form submission data contains unsanitized script tags or event handlers.
Your environment is affected if you run any AEM version below 6.5.24.0 (or below 2025.12.0) and have form fields accessible to low-privileged users without XSS validation enabled.
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. Additionally, implement input validation and output encoding on all form fields to prevent XSS attacks.
Adobe Experience Manager 6.5.24.0 or later, or Adobe Experience Manager 2025.12.0 or later
- 1. Back up your current Adobe Experience Manager instance including the repository, database, and configuration files.
- 2. Review Adobe's official upgrade documentation for AEM 6.5.24.0 or the 2025.12.0 release at helpx.adobe.com.
- 3. Ensure your system meets the prerequisites for the target version.
- 4. Perform a test upgrade in a non-production environment to validate compatibility.
- 5. Execute the upgrade to version 6.5.24.0 (for AEM 6.5 users) or to version 2025.12.0 or later.
- 6. Verify the upgrade was successful and test that the XSS vulnerability is no longer present.
- 7. Deploy the upgraded instance to production after validation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64549 — 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-64549 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