dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46877

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 6.5.23.0 / 2025.5.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Adobe 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 confidence

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload is stored in the system and executes when victims view pages containing the affected fields.

MitigationUpgrade AEM to version 6.5.23 or later. Implement output encoding on form fields and apply input validation/sanitization for user-supplied content. Consider Content Security Policy headers as defense-in-depth.

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
Experience ManagerApplication
Affected:< 6.5.23.0< 2025.5.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed AEM version
    Access the AEM System Information console at /system/console/slinglog or check the version.properties file in the crx-quickstart directory. For AEM 6.5.x, look for version 6.5.22 or earlier. For AEM as a Cloud Service or 2025 releases, look for versions before 2025.5.0.
    Affected if The installed version is below 6.5.23.0 (6.5.x line) or below 2025.5.0 (2025 release line)
  2. Identify form components accepting user input
    Review the AEM component inventory for form-based components (form, textfield, textarea, dropdown, datepicker) that store user submissions. Check the content structure under /content or /apps for form containers and their submitted data.
    Affected if Form components exist that accept and store unvalidated user input without output encoding
  3. Examine stored form data for malicious payloads
    Query the AEM repository (via CRXDE Lite at /crx/de or using the Query Builder API) for stored form submissions. Search for common XSS patterns in field values: <script, javascript:, onerror=, onload=, img src=x, SVG tags.
    Affected if Form submission data contains executable XSS payloads or suspicious script patterns
  4. Review Content Security Policy configuration
    Check the Apache Sling Content Filter or dispatcher configuration for CSP header rules. Look at /system/console/config for org.apache.sling.security.impl.ContentSecurityPolicyFilter.
    Affected if CSP is not configured or allows unsafe-inline scripts, providing no defense-in-depth mitigation

A user is affected if their AEM version is 6.5.22 or earlier, or any version below 2025.5.0, AND they have form components that store user input without output encoding or input sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.23.0 / 2025.5.0 or later
Fixed in 6.5.23.02025.5.0
Interim mitigation

Upgrade AEM to version 6.5.23 or later. Implement output encoding on form fields and apply input validation/sanitization for user-supplied content. Consider Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

AEM 6.5.23.0 or later / AEM as a Cloud Service 2025.5.0 or later

  1. 1. Identify the current Adobe Experience Manager version in use (< 6.5.23.0 for on-premise or < 2025.5.0 for Cloud Service).
  2. 2. For AEM 6.5.x on-premise installations: Plan upgrade to version 6.5.23.0 or later.
  3. 3. For AEM as a Cloud Service: Plan upgrade to version 2025.5.0 or later.
  4. 4. Review Adobe's official upgrade documentation and release notes before proceeding.
  5. 5. Perform upgrade in a non-production environment to validate compatibility.
  6. 6. After successful testing, deploy the upgrade to production.
  7. 7. Verify the XSS vulnerability is remediated by confirming the fixed version is running.
Caveat Review release notes for any migration requirements or deprecated features before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46877 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46877 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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