dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46944

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 in form fields. A low-privilege 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.

MitigationApply the vendor patch by upgrading to Adobe Experience Manager 6.5.23 or later. 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. Identify the installed Adobe Experience Manager version
    Access the AEM Web Console (usually at /system/console/configMgr) or check the product.json file in the installation directory. Alternatively, navigate to Help > About Adobe Experience Manager in the AEM welcome page.
    Affected if The installed version is earlier than 6.5.23.0 or earlier than the 2025.5.0 release.
  2. Determine if custom form components are in use
    Navigate to the CRX/DE lite (at /crx/de) and search for form-related components under /apps or /libs. Look for components containing cq:editConfig or form field definitions in the content structure.
    Affected if Custom form components exist that may not have proper output encoding applied to their input fields.
  3. Review form field input validation configuration
    In AEM, open the Edit dialog for any custom form components. Check the Validation tab or dialog properties for available validation options. Inspect thegranite:DataType constraint properties in the component's XML definition.
    Affected if Form fields lack required validation constraints or the validation is disabled.
  4. Inspect content structure for user-generated form data
    Use the Query Builder or navigate through the content tree in CRX/DE lite to locate form submission content under /content or /var. Examine the jcr:data or value properties where user input is stored.
    Affected if Form submissions are stored without sanitization and the content is rendered on published pages without encoding.

You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND your environment uses custom form components with input fields that render user-submitted data 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 the vendor patch by upgrading to Adobe Experience Manager 6.5.23 or later. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.

Recommended fix High confidence

AEM 6.5.23.0 or later; AEM as a Cloud Service 2025.5.0 or later

  1. Identify your current Adobe Experience Manager version by checking the Product Information in the AEM welcome page or system console
  2. For AEM 6.5.x deployments: Upgrade to AEM 6.5.23.0 or later by applying the latest service pack from Adobe Software Distribution (https://experience.adobe.com/#/downloads/content/software-distribution.html/aem)
  3. For AEM as a Cloud Service: Ensure your environment is updated to version 2025.5.0 or later through the Cloud Manager pipeline
  4. After upgrading, verify the fix by testing that the vulnerable form fields properly sanitize user input and no longer allow script injection
  5. Clear AEM cache and rebuild any custom applications that may have workarounds in place
Caveat Review Adobe Experience Manager 6.5.23 release notes for any breaking changes or deprecated features before upgrading; test custom workflows in non-production environment first

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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