CVE-2025-46912
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged authenticated users to inject malicious JavaScript into form fields. When other users browse to pages containing the affected fields, the malicious 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 System Information console at /system/console/status or check the version.properties file in the crx-quickstart folder. Compare the version number against the affected ranges: AEM 6.5.22 and earlier, or any version below 2025.5.0Affected if The installed version is 6.5.22 or earlier, or falls below 2025.5.0
-
Determine if the instance has form authoring enabledReview the AEM instance for deployed Adaptive Forms, Core Components with form fields, or custom form-based workflows that accept user-submitted contentAffected if Form components that accept user input are present and accessible to low-privileged authenticated users
-
Check for publicly accessible form endpointsInspect the Dispatcher configuration and publish instance to identify if form-based pages are exposed to unauthenticated or low-privileged usersAffected if Form pages are publicly accessible without requiring elevated privileges, allowing injected scripts to reach other users viewing those pages
-
Review user group permissions for form content creationExamine AEM user/group permissions to determine if low-privilege users have write access to form-enabled content pages or assetsAffected if Low-privilege users can create or edit content containing form fields where malicious scripts could be stored
An AEM instance is affected if it runs version 6.5.22 or earlier (or below 2025.5.0), has form components that accept user input, and allows low-privileged users to inject content into those form fields that other users subsequently view.
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 Adobe's official security patch (upgrade to AEM 6.5.23 or later) and implement Content Security Policy (CSP) headers as defense-in-depth to mitigate XSS execution.
Adobe Experience Manager 6.5.23.0 (for 6.5.x line) or 2025.5.0 (for 2025.x release line)
- Review Adobe Experience Manager upgrade documentation for your current version
- Ensure you have a complete backup of your AEM instance and content repository
- Test the upgrade in a non-production environment first
- Upgrade Adobe Experience Manager to version 6.5.23.0 or later (for 6.5.x line)
- Alternatively, upgrade to version 2025.5.0 or later (for 2025.x release line)
- Verify the upgrade was successful by logging into AEM
- Validate that the XSS vulnerability is resolved by testing form field inputs
- After successful testing in non-production, schedule production upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46912 — 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-46912 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