dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46939

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 where low-privileged attackers can inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing these compromised fields, the malicious script executes in their browsers.

MitigationUpgrade Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement input validation and output encoding on form fields to prevent XSS 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 the installed Adobe Experience Manager version
    Access the AEM Welcome page or use the Version HUD (/libs/granite/ui/content/shell/versionsshell.html) to view the installed product version. Alternatively, check the com.adobe.granite.package.info file in the system console or review the crx-quickstart/launchpad/config/com/adobe/granite/package.info if accessible.
    Affected if The installed version is below 6.5.23.0 or below 2025.5.0, placing it within the affected range.
  2. Verify AEM Forms module is enabled
    Navigate to the AEM Forms UI at /aem/forms or check the system console (/system/console/components) for Forms-related components. Alternatively, review the crx/de repository for /content/forms.
    Affected if The Forms module is enabled and the AEM version falls within the affected range, making stored XSS in form fields possible.
  3. Inspect form field data for suspicious content
    Access the AEM Forms data store or review form submissions in the crx/de repository under /content/forms/fp/ or similar form-related paths. Look for script tags, javascript: URIs, or event handler attributes in form field values.
    Affected if Malicious script content is found stored in form field data, confirming active exploitation of this stored XSS vulnerability.
  4. Review recent form submission logs
    Check AEM request logs and Forms audit logs (accessible via /system/console/slinglog) for unusual patterns in form submissions, particularly those containing HTML or script tags.
    Affected if Form submissions contain unescaped HTML or script content that should have been sanitized.

A user is affected if their installed Adobe Experience Manager version is below 6.5.23.0 or below 2025.5.0 and they have the Forms module enabled with user-generated form content present in the system.

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 Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement input validation and output encoding on form fields to prevent XSS injection.

Recommended fix High confidence

6.5.23.0 (for AEM 6.5.x) or 2025.5.0 (for AEM as a Cloud Service)

  1. Review the Adobe Experience Manager upgrade documentation at helpx.adobe.com for your current version
  2. Backup your AEM instance and all content repositories before proceeding
  3. Test the upgrade in a non-production environment first
  4. Upgrade AEM 6.5.x installations to version 6.5.23.0 or later
  5. Upgrade AEM as a Cloud Service installations to version 2025.5.0 or later
  6. Verify the upgrade was successful by logging into the AEM console
  7. Validate that the stored XSS vulnerability is remediated by testing the previously vulnerable form fields
Caveat Standard AEM upgrade risks apply - test thoroughly in staging before production deployment; custom code or third-party integrations may require updates

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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