dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47020

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged authenticated users to inject malicious JavaScript into form fields. The malicious payload persists in the system and executes in victims' browsers when they view pages containing the compromised form fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.23 or later to apply the security patch that addresses this vulnerability.

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 AEM product version
    Navigate to AEM Welcome page > Help > About Adobe Experience Manager, or access /system/console/configMgr/com.adobe.granite.repository.impl.jar and check the Product Version attribute. Alternatively, check the version.txt file in the crx-quickstart folder.
    Affected if The installed version is below 6.5.23.0 (for 6.5.x releases) or below 2025.5.0 (for Cloud Service/2025 releases)
  2. Identify AEM release line
    Determine if the installation is AEM 6.5 on-premise (uses 6.x.x versioning) or AEM as a Cloud Service / newer releases (uses year.month versioning like 2025.x). Check the version format shown in the About page.
    Affected if The version follows 6.5.x format and is below 6.5.23.0, OR follows 2025.x format and is below 2025.5.0
  3. Verify form submission functionality is enabled
    Review the AEM Forms or Core Components configuration. Check if any Adaptive Forms, Foundation Forms, or custom form components are created and exposed on publish instances. Access /libs/fd/af/forms and /libs/foundation/components/forms to enumerate form resources.
    Affected if Form components exist and are publicly accessible, allowing low-privileged users to submit data that gets stored in the repository

You are affected if your AEM version is below 6.5.23.0 (for 6.5.x line) or below 2025.5.0 (for newer releases) AND your system hosts form fields that accept and store user input from authenticated 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

Upgrade Adobe Experience Manager to version 6.5.23 or later to apply the security patch that addresses this vulnerability.

Recommended fix High confidence

AEM 6.5.23.0 or later; AEM 2025.5.0 or later

  1. 1. Backup your AEM instance and content repository before starting the upgrade process.
  2. 2. Review the Adobe Experience Manager 6.5.23 release notes and upgrade documentation at helpx.adobe.com for specific migration requirements.
  3. 3. Upgrade Adobe Experience Manager 6.5.x deployments to version 6.5.23.0 or later.
  4. 4. For customers on the 2024.x or newer release cadence, upgrade to version 2025.5.0 or later.
  5. 5. After upgrading, verify that all custom form components and third-party integrations function correctly.
  6. 6. Test the fixed form fields to confirm the XSS vulnerability is no longer exploitable.
Caveat Review release notes for any deprecated features or configuration changes between your current version and the target version; patch upgrades within same major version (e.g., 6.5.22 to 6.5.23) typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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