CVE-2025-64603
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 authenticated users to inject malicious JavaScript into form fields. The injected payload persists and executes in victim browsers when they 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.
-
Identify installed AEM versionAccess the AEM System Information console at /system/console/about or check the About Adobe Experience Manager page in the main menu. Locate the version number displayed.Affected if The version is 6.5.23 or earlier, or falls within the 6.5.x line before 6.5.24.0, or is identified as version 2025.12.0 or earlier.
-
Confirm AEM Forms or custom forms are in useNavigate to AEM Forms at /aem/forms or check the CRX/DE repository under /content/forms for form definitions. Identify if any adaptive forms, core components with form fields, or custom form implementations are present.Affected if Any form functionality (adaptive forms, core components, or custom forms) is enabled and contains input fields that accept user data.
-
Verify low-privileged user access to form authoringCheck user/group permissions in AEM at /useradmin. Look for groups such as 'forms-user', 'content-authors', or custom groups assigned to low-privileged accounts. Confirm they have create or modify access to form content paths.Affected if Low-privileged authenticated users (non-admin) have permissions to create, edit, or submit form content in AEM.
-
Inspect form field input validation configurationOpen form definitions in AEM Forms or CRX/DE Lite. Examine the XML or configuration of form field components (such as text fields, textareas, or number fields) for input validation and output encoding settings.Affected if Form fields lack proper input validation rules or output encoding is not configured, allowing arbitrary script execution.
Your environment is affected if you are running AEM versions before 6.5.24.0 or 2025.12.0, and low-privileged users can inject and persist unsanitized JavaScript into form fields that are displayed 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
Upgrade to Adobe Experience Manager version 6.5.24 or later to obtain the security patch. Additionally, implement input validation and Content Security Policy (CSP) headers as defense-in-depth measures.
6.5.24.0 or later (6.5.x line) or 2025.12.0 or later (2025.x line)
- Upgrade Adobe Experience Manager from the affected version (6.5.23 or earlier) to version 6.5.24.0 or later
- Alternatively, if using the 2025.x release line, upgrade to 2025.12.0 or later
- After upgrading, verify the fix by testing that malicious scripts cannot be injected into form fields
- Test the stored XSS fix by creating or editing content in vulnerable form fields with script payloads and confirming they are properly sanitized or encoded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64603 — 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-64603 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