dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47022

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 (persistent) Cross-Site Scripting vulnerability where low-privileged attackers can inject malicious JavaScript into form fields. When users view pages containing these compromised fields, the malicious script executes in their browsers.

MitigationUpgrade Adobe Experience Manager to version 6.5.23 or later, which contains the security patch for this stored XSS 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. Determine your Adobe Experience Manager version
    Access the AEM Welcome page and navigate to Help > Version Information, or append /system/console/bundles to your instance URL to view version details
    Affected if The version shown is earlier than 6.5.23.0 or earlier than 2025.5.0
  2. Confirm the exact version number
    Check the version.properties file located in the crx-quickstart folder, or view the product info in the AEM System Information console at /system/console/product
    Affected if The documented version is below 6.5.23.0 for the 6.5.x line, or below 2025.5.0 for the cloud release line
  3. Identify if custom form components store user input
    Review your project's form components in the CRX/DE repository under /apps or /libs, specifically looking for components that accept and persist user-submitted data without output encoding
    Affected if Your AEM implementation includes custom form components or adaptive forms that store unencoded user input in the repository
  4. Audit stored form field data for malicious scripts
    Use the CRXDE Lite query tool or a repository search to examine content nodes under /content that contain form field data, looking for script tags, javascript: URIs, or event handler attributes in field values
    Affected if You find script tags or JavaScript event handlers stored in form field content nodes that were not authored by administrators

You are affected if your AEM version is earlier than 6.5.23.0 or earlier than 2025.5.0 and your instance uses custom form components that accept and persist user input without proper encoding.

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, which contains the security patch for this stored XSS vulnerability.

Recommended fix Moderate confidence

6.5.23.0 (for 6.5.x branch) or 2025.5.0 (for continuous release)

  1. Review Adobe Experience Manager release notes for version 6.5.23.0 or 2025.5.0 to understand changes and requirements
  2. Create a full backup of the current AEM instance including repository content and database
  3. Set up a staging or development environment that mirrors production
  4. Test the upgrade in the non-production environment first to verify compatibility with custom code and integrations
  5. Deploy the upgrade to production following standard AEM upgrade procedures
  6. Verify the XSS vulnerability is resolved by testing the previously affected form fields
  7. Confirm that all custom workflows and integrations function correctly post-upgrade
Caveat Review release notes for potential breaking changes specific to your custom code and 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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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