CVE-2025-64826
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 XSS vulnerability where low-privileged attackers can inject malicious JavaScript into form fields. The malicious script executes in victims' browsers when they view pages containing the compromised 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 your AEM versionLocate the AEM version by accessing the system console at /system/console/status-productinfo or checking the version.properties file in the crx-quickstart folderAffected if The installed version is 6.5.23 or earlier, or falls below 6.5.24.0, or is below 2025.12.0, or is any 6.5.x release
-
Identify exposed form fieldsReview your AEM forms and content fragments that accept user input, particularly those accessible to low-privileged users such as community contributors or feedback formsAffected if Form fields that capture user input are publicly accessible without proper input validation or output encoding
-
Inspect stored form content for script payloadsQuery the JCR repository (using CRXDE Lite at /crx/de or a repository search) for form component nodes and inspect the stored values for suspicious script tags, javascript: URIs, or event handler attributesAffected if Any form field values contain unescaped HTML script tags or JavaScript event handlers
-
Check for low-privileged user access to formsReview user and group permissions in the AEM user administration at /security/users.html or /security/groups.html to identify low-privilege accounts that have access to form creation or editingAffected if Users with limited permissions (such as contributors or community members) can create or modify form content
-
Verify output encoding on form componentsExamine your form component configurations in the AEM component registry or in the HTML source of rendered form pages to confirm whether output encoding is applied to user-submitted field valuesAffected if Form fields render user input without HTML entity encoding (the raw input displays as-is in the browser)
You are affected if your AEM version is 6.5.23 or earlier, or any 6.5.x version below 6.5.24.0, or below 2025.12.0, and you have form fields accessible to low-privileged users that render stored content without output 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
Upgrade to AEM 6.5.24 or later to receive the vendor patch. Alternatively, implement output encoding and input validation on affected form fields until the upgrade can be applied.
AEM 6.5.24.0 or later (or 2025.12.0 release train)
- Verify current Adobe Experience Manager version by accessing the AEM welcome page or checking the version properties in the crx-quickstart folder
- Review the Adobe Experience Manager 6.5 release notes and upgrade documentation at helpx.adobe.com for upgrade procedures
- Ensure you have a complete backup of the AEM instance, including the repository, database, and configuration files
- Test the upgrade in a non-production environment before deploying to production
- Follow Adobe's recommended upgrade path for AEM 6.5, which typically involves stopping the instance, replacing the jar file with version 6.5.24.0 or later, and restarting
- After upgrade, verify that the stored XSS vulnerability is resolved by testing the vulnerable form fields that were previously identified
- Review user permissions and form field configurations to ensure proper sanitization is in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64826 — 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-64826 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