CVE-2025-64623
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. Low-privileged authenticated users can inject malicious JavaScript payloads into form input fields, which persist on the server. When other users subsequently view pages containing these compromised form fields, the injected script executes in their browsers, potentially enabling session hijacking or data theft.
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 AEM versionAccess the AEM welcome page or check the product version via the Help menu, or query the version endpoint at /system/console/bundles if accessible. Compare the installed version against the affected ranges: versions below 6.5.24.0, versions below 2025.12.0, or exactly version 6.5 are vulnerable.Affected if Installed version is < 6.5.24.0, < 2025.12.0, or equals 6.5
-
Identify accessible form componentsReview the AEM instance for deployed forms that accept user input, such as Adaptive Forms, Form fragments, or custom form components in the /content directory. Check /libs/fd/af for Adaptive Forms components.Affected if Forms accepting user input are published and accessible to authenticated low-privilege users
-
Verify low-privilege user access to form authoringLog in with a test low-privilege user account (for example, a user with only content-author permissions) and attempt to access form editing or creation interfaces at /aem/forms or through the Forms workspace.Affected if Low-privilege users can access or edit form fields in AEM
-
Inspect stored form data for malicious payloadsQuery the AEM repository (via CRXDE Lite at /crx/de or the Query tool) for any suspicious script tags or JavaScript event handlers within form field content nodes under /content, for example searching for <script, javascript:, or onerror= patterns in form submission data.Affected if Form data stored in the repository contains unsanitized script tags or event handlers that could execute in a victim's browser
The environment is affected if the installed AEM version falls within the vulnerable ranges AND forms with user input fields are accessible to low-privileged authenticated 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 Adobe security patch or upgrade to AEM 6.5.24 or later. After patching, conduct security testing to verify form fields properly sanitize user input and the stored XSS vector is neutralized.
6.5.24.0 or later (for 6.5.x line); or 2025.12.0 or later
- Identify your current Adobe Experience Manager version from the AEM Dashboard or system information
- Download Adobe Experience Manager 6.5.24.0 or later from the official Adobe distribution channel (software-distribution.adobe.com)
- Review the Adobe Experience Manager 6.5.24 release notes for any pre-upgrade requirements
- Create a complete backup of your AEM instance including the repository, database, and configurations
- Test the upgrade in a non-production environment before applying to production
- Stop the AEM instance and run the upgrade installer
- After successful upgrade, verify the form fields that were vulnerable are now properly sanitizing input
- Clear all caches and rebuild any custom indexes as needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64623 — 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-64623 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