dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46914

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 in form fields. A low-privileged attacker can inject malicious JavaScript payloads into vulnerable form inputs, which persist on the page and execute in victim users' browsers when they view the affected content.

MitigationImplement proper input validation and output encoding on all form fields in AEM, prioritizing context-aware sanitization. Consider using AEM's built-in XSS protection mechanisms andContent Security Policy headers.

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 AEM product version
    Access the AEM welcome page or use the version info endpoint (e.g., /system/console/components or check the quickstart properties file). Compare the installed version 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.
  2. Identify custom form components
    Review the /apps directory for any custom form components, parsys configurations, or user-generated content forms that accept input. Check both /libs and /apps for form-related components that may be exposed to low-privileged users.
    Affected if Custom or out-of-the-box form components that accept user input are present and accessible to low-privileged users.
  3. Inspect form field input validation
    Examine the HTL templates or JSP scripts associated with the form components in use. Look for the presence of context-aware output encoding or server-side input validation on form field submissions.
    Affected if Form fields lack proper input validation or output encoding is not applied in the component templates.
  4. Review stored content for malicious payloads
    Query the repository (via CRXDE Lite or a content search) for script tags, javascript: URIs, or event handler attributes within form-related content nodes or user-generated content fields.
    Affected if Suspicious JavaScript payloads or XSS vectors are found stored in form-related content nodes.

Your AEM instance is affected if it runs version 6.5.22 or earlier (or pre-2025.5.0) and exposes any form fields to low-privileged users without proper input validation and 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

Implement proper input validation and output encoding on all form fields in AEM, prioritizing context-aware sanitization. Consider using AEM's built-in XSS protection mechanisms andContent Security Policy headers.

Recommended fix High confidence

AEM 6.5.23.0 (on-premise) or AEM 2025.5.0 (cloud)

  1. Identify your current Adobe Experience Manager version and deployment type (on-premise or cloud)
  2. For AEM 6.5.x on-premise: Upgrade to version 6.5.23.0 or later
  3. For AEM Cloud: Upgrade to version 2025.5.0 or later
  4. After upgrade, verify the XSS fix is applied by reviewing Adobe's security bulletin for CVE-2025-46914
  5. Test that form fields properly sanitize user input to prevent stored XSS attacks
  6. Ensure low-privileged users cannot inject malicious scripts into form fields post-upgrade
Caveat Adobe point releases typically include backward-compatible fixes; review release notes for any configuration or API changes

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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