dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46918

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

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. A low-privileged authenticated user can inject malicious JavaScript into form fields, which persists in the system. When other users view pages containing the affected form fields, the injected script executes in their browsers, potentially allowing session hijacking or credential theft.

MitigationApply the official Adobe security patch by updating to AEM 6.5.23 or later. Validate that all form inputs are properly sanitized and consider implementing Content Security Policy (CSP) 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. Determine AEM version
    Access the AEM System Information console at /system/console/system or check the crx-quickstart folder for the version.properties file to identify the installed AEM version number
    Affected if The installed version is lower than 6.5.23.0 for the 6.5.x branch or lower than 2025.5.0 for the cloud release branch
  2. Identify custom form implementations
    Review the AEM Forms or custom form components in use by examining the /apps directory structure for custom form field components or adaptive form configurations
    Affected if Custom form components or adaptive forms that accept user input are deployed in the environment
  3. Audit form data storage
    Examine content repositories (typically under /content or custom content paths) where form submission data is stored, looking for any script tags or JavaScript code within text input fields
    Affected if Any form field data contains unescaped HTML script tags or JavaScript event handlers that could execute in a user's browser
  4. Review recent user content
    Query the AEM content repository for recent entries in form-enabled pages or form submission nodes, particularly looking for submissions from low-privilege users
    Affected if Form submissions from standard or contributor-level users contain suspicious markup or script content

You are affected if your AEM installation version is below 6.5.23.0 or below 2025.5.0 AND you have form fields that accept user input and display that content to other users without 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

Apply the official Adobe security patch by updating to AEM 6.5.23 or later. Validate that all form inputs are properly sanitized and consider implementing Content Security Policy (CSP) headers as defense-in-depth.

Recommended fix High confidence

AEM 6.5.23.0 (for 6.5.x branch) or AEM 2025.5.0 (for Cloud Service/continuous release)

  1. Verify current AEM version in use by checking the About Adobe Experience Manager page in the OSGi console
  2. Determine which release line applies: AEM 6.5.x (on-premises) or AEM as a Cloud Service (2025.x release line)
  3. For AEM 6.5.x: Plan upgrade to version 6.5.23.0 or later
  4. For AEM as a Cloud Service: Plan upgrade to 2025.5.0 or later
  5. Review Adobe's upgrade documentation for your deployment type before proceeding
  6. Create a backup of the current AEM instance and content repository
  7. Test the upgrade in a non-production environment first
  8. Execute the upgrade following Adobe's recommended upgrade procedure
Caveat Review Adobe's 6.5.23 or 2025.5 release notes for potential breaking changes to custom code, integrations, 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-46918 — 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-46918 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