dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47050

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 attacker can inject malicious JavaScript into vulnerable form input fields, which is then stored in the system. When other users browse to pages containing these affected fields, the malicious script executes in their browsers.

MitigationApply the vendor patch (AEM 6.5.23 or later). Until patched, implement output encoding on form field outputs and input validation on form field inputs to neutralize malicious script content.

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 installed AEM version
    Access the AEM System Information console at /system/console/status ProductInfo or check the crx/packmgr/installed.jsp endpoint to view the installed AEM version number
    Affected if The installed version is below 6.5.23.0 or below 2025.5.0 (for AEM as a Cloud Service)
  2. Identify custom form components in use
    Review the /apps directory for custom form components or check content pages that render HTML forms. Look for components under /apps that extend core form components or implement custom form field rendering
    Affected if Custom form components exist that may not apply proper output encoding to user input
  3. Inspect form field output encoding
    Review JSP, HTL, or Java templates that render form field values. Check if the form field output uses proper encoding methods such as encoding utilities (XSS API) or framework-provided encoding functions
    Affected if Form field templates render user-supplied values without applying HTML encoding or XSS protection
  4. Audit form input validation configuration
    Check the form field validation rules in the component dialogs (.xml files under /apps) or custom validation logic to determine if input validation is configured to reject script tags and other potentially malicious payloads
    Affected if No input validation rules exist or validation does not strip script-related characters

You are affected if your AEM version is below 6.5.23.0 (or below 2025.5.0 for cloud) AND your form fields render stored user input without output encoding or input validation.

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 (AEM 6.5.23 or later). Until patched, implement output encoding on form field outputs and input validation on form field inputs to neutralize malicious script content.

Recommended fix High confidence

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

  1. 1. Review Adobe Experience Manager upgrade documentation for your current version at helpx.adobe.com
  2. 2. Perform a full backup of your AEM instance including repository, database, and configurations
  3. 3. Test the upgrade in a non-production environment before applying to production
  4. 4. For AEM 6.5.x installations: upgrade to version 6.5.23.0 or later
  5. 5. For AEM as a Cloud Service: upgrade to version 2025.5.0 or later
  6. 6. After upgrade, verify that the XSS filter configurations are functioning correctly
  7. 7. Test that form fields properly sanitize user input to prevent XSS
  8. 8. Validate the upgrade in staging before deploying to production
Caveat Review Adobe's release notes for breaking changes between your current version and 6.5.23.0; test custom code and integrations for compatibility

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