dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47007

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 input areas, which persist on the page. When other users (including administrators) view the affected page, the malicious script executes in their browsers, potentially stealing session cookies or performing actions on behalf of the victim.

MitigationApply the vendor patch (AEM 6.5.23 or later). Until patched, disable or restrict low-privilege user access to vulnerable form fields and implement Content Security Policy headers to mitigate XSS execution.

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 the installed AEM version
    Navigate to AEM Welcome page > Tools > Operations > Diagnosis, or access /system/console/configMgr and check the Product Info component. Alternatively, check the crx-quickstart/package.properties file for the version property.
    Affected if The installed version is 6.5.22 or earlier, or the version is below 2025.5.0
  2. Identify form fields accessible to low-privilege users
    Review user group permissions in AEM Users or Groups console (access via /security/users.html or /security/groups.html). Check which groups have create/modify permissions on content fragments, experience fragments, or adaptive form fragments under /content.
    Affected if Low-privilege users (non-admin) have write access to form-based content paths
  3. Inspect stored form data for existing XSS payloads
    Query the JCR repository using CRXDE Lite (accessible at /crx/de) or the Query tool. Search for common XSS patterns in content nodes, such as <script, javascript:, onload=, onerror=, or encoded variants in form field values under /content.
    Affected if Malicious script tags or event handlers are found persisted in form content nodes
  4. Review Content Security Policy headers
    Use browser developer tools (Network tab) or a tool like curl to inspect HTTP response headers when accessing AEM pages. Look for Content-Security-Policy header and evaluate if it restricts inline scripts.
    Affected if No CSP header is set, or CSP allows unsafe-inline, enabling XSS execution

A user is affected if their AEM version is below 6.5.23.0 or 2025.5.0 AND low-privilege users have access to form fields that can store and display user-supplied content to other users.

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, disable or restrict low-privilege user access to vulnerable form fields and implement Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 (or later 6.5.x) or Adobe Experience Manager 2025.5.0 (or later)

  1. Review Adobe's official upgrade documentation for Adobe Experience Manager on helpx.adobe.com
  2. Create a complete backup of the current AEM instance including content and configuration
  3. Test the upgrade in a non-production/staging environment first
  4. Download and install Adobe Experience Manager version 6.5.23.0 or later for the 6.5.x line, or version 2025.5.0 or later for the cloud release line
  5. Verify the upgrade was successful by logging into AEM
  6. Confirm the XSS vulnerability is resolved by testing that malicious scripts cannot be injected into form fields
  7. Deploy the upgraded version to production after successful validation
Caveat Standard AEM upgrade best practices apply; review Adobe's release notes for any configuration or compatibility changes 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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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