dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47070

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

AEM versions 6.5.22 and earlier contain a stored XSS vulnerability in form fields where a low-privileged attacker can inject malicious JavaScript that persists in the system and executes when other users view the affected pages.

MitigationApply the vendor patch for AEM 6.5.22 or later. Until patched, sanitize all form inputs 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. Determine installed AEM version
    Access the AEM version information via the System Overview console at /system/console/configMgr/com.adobe.granite.package.impl, or check the version.properties file in the crx-quickstart directory
    Affected if Version is below 6.5.23.0 for AEM 6.5.x releases, or below 2025.5.0 for the newer release cadence
  2. Identify active form implementations
    Review AEM instances for deployed form components including Adaptive Forms, Core Components form fields, or custom form implementations in /apps and /content
    Affected if Form components that accept user input are present and accessible to users in the system
  3. Inspect form submission repositories for unsanitized content
    Query form data stored in CRXDE under /content/forms or custom form submission paths. Look for entries containing unescaped HTML script tags or JavaScript event handlers in submitted values
    Affected if Stored form data contains raw script tags or javascript: URIs that could execute in other user sessions
  4. Verify user access controls on form-enabled paths
    Review ACLs and permission configurations in AEM for paths containing forms. Check if low-privileged users (contributors, authors without admin rights) have create or modify access to form content
    Affected if Non-admin users have write access to form-enabled content paths where malicious scripts could be injected and stored

Your environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 AND forms accepting user input are present in the system where low-privileged users can submit content.

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 for AEM 6.5.22 or later. Until patched, sanitize all form inputs and implement Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

AEM 6.5.23.0 (for on-premise 6.5.x) or AEM 2025.5.0 (for cloud)

  1. 1. Back up the current Adobe Experience Manager instance including repository, database, and configuration files.
  2. 2. Review the Adobe Experience Manager 6.5.23.0 release notes for any migration or compatibility requirements.
  3. 3. Download Adobe Experience Manager 6.5.23.0 (or 2025.5.0 for cloud version) from the official Adobe distribution portal.
  4. 4. Stop the running AEM instance.
  5. 5. Install the updated AEM version following Adobe's standard upgrade documentation.
  6. 6. Verify all custom workflows, templates, and integrations function correctly after upgrade.
  7. 7. Test that the XSS vulnerability is remediated by attempting to inject script content into form fields.
Caveat Review release notes for potential breaking changes in custom components, workflows, or third-party integrations before upgrading

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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