dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47004

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 · moderate confidence

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting vulnerability where low-privileged users can inject malicious JavaScript into form fields. The injected script persists on the page and executes in victim browsers when they navigate to the affected content.

MitigationUpgrade to a patched AEM version (6.5.23 or later), or implement strict input validation and output encoding on all form fields to neutralize malicious script payloads.

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
    Navigate to the AEM Welcome page and click 'About Adobe Experience Manager', or access the system console at /system/console/configMgr and look for the version information banner
    Affected if The displayed version is earlier than 6.5.23.0 or earlier than 2025.5.0 (for cloud/future releases)
  2. Identify low-privileged user access
    Review user groups and permissions in AEM User Management at /security/users.html or /libs/granite/security/content/useradmin to identify users with contributor or author-level access to form content
    Affected if Low-privileged users have write access to form-enabled content pages or experience fragments
  3. Audit form-enabled content for injected scripts
    Use the AEM Query Builder or CRX/DE Lite at /crx/de to search content nodes under /content for stored script tags - search for patterns like '<script', 'javascript:', 'onerror=', 'onload=' in form field values
    Affected if Any form fields contain unsanitized script tags or event handler attributes in the content repository
  4. Inspect published pages that render form data
    Navigate to publicly accessible pages that display form field content and view the page source to verify if user-submitted values are rendered without output encoding
    Affected if Form data appears in the HTML output without proper escaping or encoding

You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged users can submit form content that gets rendered without sanitization, allowing stored XSS payloads to execute in other users' browsers.

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 to a patched AEM version (6.5.23 or later), or implement strict input validation and output encoding on all form fields to neutralize malicious script payloads.

Recommended fix High confidence

Upgrade to AEM 6.5.23.0 or later, or to AEM as a Cloud Service 2025.5.0 or later

  1. Identify your current Adobe Experience Manager version by checking the Product Information page in AEM or the version.properties file
  2. Download Adobe Experience Manager 6.5.23.0 or later from the Adobe Distribution Package or Software Distribution portal
  3. Review the Adobe Experience Manager 6.5.23.0 release notes for any known issues and prerequisites
  4. Perform a full backup of your AEM instance including the repository, database, and configuration files
  5. Test the upgrade in a non-production environment before applying to production
  6. Execute the upgrade following Adobe's standard upgrade documentation procedures
  7. After upgrade, verify that the XSS vulnerability is resolved by testing the affected form fields
  8. Clear browser cache and AEM dispatcher cache after upgrade
Caveat Review AEM 6.5.23.0 release notes for any compatibility issues 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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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