dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46893

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager 6.5.22 and earlier allows low-privilege attackers to inject malicious JavaScript into form fields. The malicious payload persists on the server and executes in victims' browsers when they view affected pages.

MitigationApply Adobe's security patch (AEM 6.5.23 or later) to address the vulnerability. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.

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 console at /system/console/status-AEMProductInfo or check the About Adobe Experience Manager page (Help > About). Note the exact version number displayed.
    Affected if The version is less than 6.5.23.0 (for 6.5.x branch) or less than 2025.5.0 (for cloud/release branch)
  2. Verify AEM 6.5.x version if applicable
    If running the 6.5.x release line, confirm the full version string includes 6.5.23.0 or later. Versions 6.5.22.0 and earlier are affected.
    Affected if Running AEM 6.5.22.0 or any earlier 6.5.x version
  3. Verify AEM 2025.x version if applicable
    If running the 2025 release line, confirm the version is 2025.5.0 or later. Versions before 2025.5.0 are affected.
    Affected if Running any AEM 2025.x version prior to 2025.5.0
  4. Identify custom or adaptive forms accepting user input
    Review form components in AEM content structures. Check for Adaptive Forms, Core Components with form fields, or custom form implementations under /content or /apps that accept user-submitted data.
    Affected if Forms exist that accept user input and the AEM version is within the affected ranges
  5. Check form field output encoding
    Submit a benign test payload (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>) into a form field and then view the submitted data or the page containing that data. Inspect the page source to see if the payload is rendered as plain text or executed as JavaScript.
    Affected if The test payload executes as JavaScript when viewed, indicating lack of output encoding

You are affected if your AEM version is below 6.5.23.0 (6.5.x branch) or below 2025.5.0 (2025 branch) and you have form fields that accept user input without proper output encoding.

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

Apply Adobe's security patch (AEM 6.5.23 or later) to address the vulnerability. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.

Recommended fix High confidence

6.5.23.0 (LTS) or 2025.5.0 (modern release)

  1. 1. Identify current Adobe Experience Manager version via /system/console/config or AEM startup logs
  2. 2. Determine which release track you're on (6.5.x LTS or 2025.x cloud-aligned releases)
  3. 3. Review Adobe Experience Manager 6.5.23 release notes for your specific deployment type
  4. 4. Create a full backup of AEM repository (crx-quickstart) and database
  5. 5. Test upgrade in a non-production environment first
  6. 6. Schedule maintenance window and inform users
  7. 7. Run the upgrade installer for version 6.5.23.0 (for 6.5.x track) or 2025.5.0 (for modern release track)
  8. 8. After upgrade, clear dispatcher cache and browser caches
Caveat AEM major version upgrades may require code changes; review 6.5.23 release notes for regression notices and ensure custom code compatibility before production deployment

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

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