dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47011

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-privileged authenticated attacker can inject malicious JavaScript payloads into vulnerable form input fields, which then executes in the browsers of subsequent users who view pages containing the compromised data.

MitigationApply the Adobe security patch for AEM 6.5.22 or later; if unavailable, implement output encoding/validation on affected form fields and consider WAF rules to detect XSS attempts.

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 AEM version
    Access the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the crx-quickstart directory
    Affected if The installed version is 6.5.22 or earlier, or falls below 2025.5.0
  2. Verify Forms module is enabled
    Navigate to AEM Forms settings at /aem/forms or check the Forms functionality via the AEM Felix console at /system/console/bundles
    Affected if The Forms module is active and accessible to authenticated users
  3. Confirm low-privileged user access to form fields
    Review user group permissions in AEM User Manager at /useradmin - check if contributors or content-authors can access and modify form input fields
    Affected if Users with limited (contributor/author) roles can create or edit form field data
  4. Inspect form data for malicious payloads
    Query the AEM repository (via CRXDE Lite at /crx/de or repository explorer) or export form submission data to search for script tags, javascript: URIs, or event handler attributes in stored values
    Affected if Form field entries contain unsanitized HTML/script content that could execute in other users browsers
  5. Review published content for XSS indicators
    Check pages that render form data (such asThank You pages or confirmation screens) using browser developer tools to inspect the DOM for unencoded user-supplied values
    Affected if User-provided form data appears in page output without proper HTML encoding

You are affected if your AEM installation version is below 6.5.23.0 or 2025.5.0 AND your Forms functionality is accessible to authenticated users who can inject and store malicious scripts into form input fields.

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 Adobe security patch for AEM 6.5.22 or later; if unavailable, implement output encoding/validation on affected form fields and consider WAF rules to detect XSS attempts.

Recommended fix High confidence

AEM 6.5.23.0 or AEM 2025.5.0 (depending on your release track)

  1. 1. Back up the current Adobe Experience Manager instance, including the repository, database, and configuration files.
  2. 2. Review Adobe's official upgrade documentation for AEM 6.5.23 or AEM 2025.5.0 at helpx.adobe.com.
  3. 3. Ensure all custom code and third-party integrations are compatible with the target version.
  4. 4. Perform the upgrade following Adobe's recommended upgrade procedure for your deployment model.
  5. 5. After upgrade, verify that all form fields and user-generated content areas are properly sanitizing input.
  6. 6. Test the application thoroughly to confirm the XSS vulnerability is remediated.
  7. 7. Validate that existing workflows and authoring functionalities remain operational.
Caveat Review Adobe's release notes for 6.5.23.0 and 2025.5.0 for any deprecation notices or breaking changes that may affect custom components or integrations

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-47011 — 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-47011 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