CVE-2025-46862
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 · moderate confidenceAdobe Experience Manager versions 6.5.22 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript into vulnerable form inputs, which persists on the page. When other users view pages containing these compromised 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.
-
Verify Adobe Experience Manager versionAccess the AEM Welcome page or check the product version through the system information console (Help > System Information). Compare the version number against the affected ranges: < 6.5.23.0 or < 2025.5.0.Affected if The installed version is 6.5.22 or earlier, or falls below 2025.5.0 for the newer release line.
-
Identify deployed form componentsReview the AEM instance for pages that use form fields (form components, adaptive forms, or custom form implementations). Check the CRX/DE repository under /apps or /content for form-related components.Affected if Form fields or adaptive forms are deployed and accessible to low-privileged users.
-
Audit form field input storageQuery the repository or database for form field submissions. Use the AEM Query Builder or directly inspect content nodes under /content that store form data. Look for unexpected HTML or script tags within form field values.Affected if Form submissions contain raw HTML, script tags, or JavaScript event handlers stored as field values.
-
Review low-privileged user access to formsCheck user group permissions in AEM under Tools > Security > Permissions. Verify if users with limited privileges (contributors, authors without admin rights) can create or edit form content.Affected if Low-privileged users have permission to submit or edit content in form-enabled areas.
A user is affected if their AEM version is below 6.5.23.0 (or below 2025.5.0) AND the system hosts form fields accessible to low-privileged users where unsanitized input could be stored.
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
Update Adobe Experience Manager to version 6.5.23 or later, or apply the corresponding security patch to remediate the stored XSS vulnerability.
AEM 6.5.23.0 or later; AEM 2025.5.0 or later
- Verify the current Adobe Experience Manager version in use by accessing the AEM Welcome page or checking the version.properties file
- Identify whether the deployment is AEM 6.5.x or AEM 2025.x branch
- For AEM 6.5.x deployments: Plan upgrade to version 6.5.23.0 or later
- For AEM 2025.x deployments: Plan upgrade to version 2025.5.0 or later
- Review Adobe's official upgrade documentation for the target version
- Test the upgrade in a non-production environment before deploying to production
- Schedule maintenance window for the upgrade process
- Perform a full backup of the AEM repository (segment store, datastore, and database)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46862 — 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-46862 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