dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46879

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 · moderate confidence

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. Low-privileged authenticated users can inject malicious JavaScript payloads into vulnerable form fields. When other users subsequently browse to pages containing these compromised fields, the malicious script executes in their browsers, potentially allowing session hijacking, data theft, or actions on behalf of the victim.

MitigationUpdate Adobe Experience Manager to version 6.5.23 or later. Alternatively, implement strict input validation and output encoding on all form fields to prevent script injection.

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. Determine installed AEM version
    Access the AEM system information page at /system/console/status-productinfo or check the version.properties file in the crx-quickstart directory. You can also run: curl -s https://[hostname]:[port]/system/console/status-productinfo | grep -i version
    Affected if The installed version is below 6.5.23.0 or below 2025.5.0 (for cloud/2025 releases)
  2. Identify form components in use
    Review the AEM content structure under /content or /apps for form components such as core WCM components (core/wcm/components/form), foundation components, or custom form implementations. Use CRX/DE or search for nodes containing 'form' in the content tree.
    Affected if Form fields that accept user input are present and accessible to low-privileged users without proper output encoding
  3. Audit low-privileged user permissions
    Navigate to AEM Tools > Security > Permissions or check user group memberships in /home/groups. Verify whether standard authors or contributors have write access to form-enabled content pages.
    Affected if Low-privileged users (authors, contributors, or custom groups) have permission to create or edit content containing form fields
  4. Scan for existing XSS payloads in content
    Use AEM Query Builder or search crx/de to query content nodes for suspicious patterns. Example QueryBuilder URL: /bin/querybuilder.json?type=nt:unstructured&1_property=jcr:content&1_value=<script. Search for common XSS patterns like <script, javascript:, onerror=, onload=, and event handlers.
    Affected if Any content nodes contain encoded or unencoded JavaScript payloads in form-related fields

Your environment is affected if the AEM version is below 6.5.23.0 (or below 2025.5.0 for newer releases) AND low-privileged authenticated users can access and modify form fields, as the stored XSS can only be exploited when malicious scripts are injected into these fields and later rendered to other users.

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

Update Adobe Experience Manager to version 6.5.23 or later. Alternatively, implement strict input validation and output encoding on all form fields to prevent script injection.

Recommended fix High confidence

6.5.23.0 or later for 6.5.x line; 2025.5.0 or later for 2025.x line

  1. Check the current Adobe Experience Manager version in use (typically found in the AEM Web Console or about page)
  2. If running version 6.5.22 or earlier (6.5.x line), plan upgrade to version 6.5.23.0 or later
  3. If running a 2025.x version earlier than 2025.5.0, plan upgrade to version 2025.5.0 or later
  4. Review Adobe's official release notes and upgrade documentation for the target version
  5. Create a full backup of the AEM instance and content repository before upgrading
  6. Test the upgrade in a non-production/staging environment first
  7. Schedule the upgrade during a planned maintenance window
  8. Perform the upgrade following Adobe's recommended upgrade procedure

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46879 — 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-46879 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