CVE-2025-46926
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.22 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.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where low-privileged attackers can inject malicious JavaScript into form fields. When victims browse to pages containing these compromised fields, the injected scripts execute in their browsers, enabling session hijacking, credential theft, or defacement.
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.23.0< 2025.5.0CVSS 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 the installed AEM versionNavigate to the AEM Welcome page or check the product version via the system console (Help > About Adobe Experience Manager). Compare the version number to the affected ranges: versions below 6.5.23.0 or below 2025.5.0.Affected if The installed version is 6.5.22 or earlier, or falls between 6.5.23.0 and 2025.5.0 (exclusive).
-
Identify form fields that accept user inputReview the AEM Forms or content fragment configurations in use. Check which form components, adaptive forms, or content models include input fields that store data in the repository.Affected if Form fields are present and store user-submitted data without server-side input validation configured.
-
Verify low-privilege user access to form editingInspect the permissions for low-privileged users (such as authors or contributors) in the AEM Users or Groups console. Check if these users can create or edit form components, adaptive forms, or content fragments.Affected if Low-privilege users have permission to create or modify form fields in the AEM instance.
-
Inspect stored form data for malicious payloadsQuery the repository (via CRXDE Lite or AEM Query Builder) for stored form submissions or content containing script tags, javascript:, or other XSS patterns in form field values.Affected if Stored form data contains unsanitized script tags or JavaScript event handlers in field values.
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged users can inject script content into form fields that get stored and rendered 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.23.02025.5.0
Apply the vendor patch for AEM 6.5.22 or later. Until patched, implement input validation and output encoding on affected form fields, and consider deploying a WAF rule to filter XSS payloads in form submissions.
Adobe Experience Manager 6.5.23.0 (on-premise) or 2025.5.0 (cloud)
- 1. Review Adobe Experience Manager release notes for version 6.5.23.0 (or 2025.5.0 for cloud releases) to understand changes and prerequisites
- 2. Back up the current AEM instance including the repository, database, and configuration files
- 3. Schedule a maintenance window as upgrade will require downtime
- 4. For AEM 6.5.x on-premise: Download and install AEM 6.5.23.0 from Adobe Software Distribution or your license portal
- 5. For AEM Cloud: The fix will be applied automatically with the next deployment after version 2025.5.0
- 6. After upgrade, verify the form fields that were previously vulnerable are now properly sanitizing input
- 7. Test critical user workflows to ensure functionality is intact post-upgrade
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-46926 — 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-46926 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