CVE-2025-46951
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 are vulnerable to stored Cross-Site Scripting (XSS), allowing low-privileged attackers to inject malicious JavaScript into form fields. When victims browse pages containing these 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.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.
-
Identify installed AEM versionAccess the AEM Welcome page or check the version via the system information console at /system/console/bundles, or run 'aem -version' if using the command lineAffected if The installed version is earlier than 6.5.23.0 or earlier than 2025.5.0 (for the 2025 release track)
-
Confirm Forms or form authoring is enabledNavigate to the AEM Forms console at /aem/forms or check if the 'aem-forms' bundle is active in /system/console/bundlesAffected if Forms functionality is enabled and the version check shows a vulnerable release
-
Verify low-privileged user access to FormsCheck user permissions in the AEM User Administration console at /useradmin to see if non-admin users have create or edit permissions on form content nodesAffected if Low-privilege users (such as content authors or regular users) have permission to create or edit form fields
-
Audit existing form field content for malicious scriptsQuery the JCR (Java Content Repository) for form field nodes using CRXDE Lite at /crx/de or the Query tool searching for content under /content/forms with script tags in text valuesAffected if Any form fields contain unsanitized HTML or JavaScript content, particularly script tags or event handlers like onload/onerror
A user is affected if their AEM version is below 6.5.23.0 or below 2025.5.0 AND they have Forms enabled with low-privileged user access, or if malicious scripts already exist in form fields.
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
Upgrade Adobe Experience Manager to version 6.5.23 or later to apply vendor patches; additionally implement output encoding and input validation on vulnerable form fields.
AEM 6.5.23.0 (for 6.5.x branch) or AEM 2025.5.0 (for newer release train)
- Identify which AEM release train your instance is on (6.5.x or 2024.x/2025.x branch)
- If running 6.5.x branch: Upgrade to AEM 6.5.23.0 or later
- If running the newer release train: Upgrade to 2025.5.0 or later
- After upgrading, verify that the stored XSS vulnerability is patched by testing the vulnerable form fields
- Confirm that malicious scripts in form field input are properly sanitized and not executed in victim browsers
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46951 — 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-46951 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