CVE-2025-46858
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 in form fields. Low-privileged authenticated users can inject malicious JavaScript payloads into vulnerable form inputs, which are stored in the system and execute in the browsers of other users who view the affected pages.
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.
-
Determine AEM versionAccess the AEM Welcome page or check the product.info.json endpoint (e.g., /system/console/product.json) to identify the exact installed version of Adobe Experience Manager.Affected if The installed version is less than 6.5.23.0 or less than 2025.5.0, placing it within the affected range.
-
Identify deployed forms with user inputReview the AEM Forms or Adaptive Forms configurations in the AEM Assets or Foundation components. Check for form components (such as text fields, text areas, or other input fields) that store user-submitted data.Affected if Form components that accept and store user input are deployed and accessible within the AEM environment.
-
Verify low-privileged user access to formsReview user permissions and group assignments in AEM to confirm whether low-privileged or standard users have access to create, edit, or submit form content.Affected if Low-privileged authenticated users can access and submit data through vulnerable form fields, allowing injection of malicious payloads.
-
Check for stored form submissionsInspect the AEM content repository (via CRXDE Lite or Content Services) for stored form submission data that may contain unsanitized user input in form fields.Affected if Stored form submissions exist in the repository that could contain malicious JavaScript payloads waiting to be rendered.
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged users can access and submit data through form fields that store user input.
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 remediate the stored XSS vulnerability. Additionally, implement input validation and output encoding on form fields as a defense-in-depth measure.
AEM 6.5.23.0 or AEM 2025.5.0 and later
- Back up the current AEM instance including the repository, configuration, and any custom code
- Review Adobe's official upgrade documentation for your current version
- Download Adobe Experience Manager 6.5.23.0 or 2025.5.0 (or later) from the official Adobe distribution portal
- Test the upgrade in a non-production environment first to verify compatibility with custom components and integrations
- Deploy the upgrade to production following standard AEM upgrade procedures
- Verify that the XSS vulnerability is remediated by testing the previously vulnerable form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46858 — 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-46858 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