dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47042

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 where low-privileged authenticated users can inject malicious JavaScript into form fields. The payload persists on the server and executes when other users view the affected page, allowing session hijacking, credential theft, or defacement.

MitigationUpgrade Adobe Experience Manager to a version newer than 6.5.22, or apply the vendor-supplied patch. Additionally, implement output encoding and input validation on form fields, and consider adding 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. Identify AEM version
    Access the AEM system information page at /system/console/configMgr or check the com.adobe.granite.product.version property in the OSGi console. Alternatively, look for the version file in the installation directory or check the About Adobe Experience Manager page from the main navigation.
    Affected if The installed version is below 6.5.23.0 or below 2025.5.0
  2. Verify Forms or content editing is enabled
    Check if AEM Forms, Adaptive Forms, or Content Fragment functionality is enabled by navigating to the Features console or checking the OSGi configuration for com.adobe.granite.ui.clientlibs or related form packages.
    Affected if Forms or content fragment creation/modification features are active and accessible to users
  3. Confirm low-privileged user access to form fields
    Log in with a low-privileged test account (such as a standard user with only contributor or author permissions) and attempt to access form-based components or content fragment fields. Check if the user can create or edit content containing form input fields.
    Affected if Low-privileged authenticated users have the ability to create or edit form fields or content fragments

Your environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 and form fields or content editing capabilities are accessible to low-privileged 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 a version newer than 6.5.22, or apply the vendor-supplied patch. Additionally, implement output encoding and input validation on form fields, and consider adding Content-Security-Policy headers to mitigate XSS execution.

Recommended fix High confidence

6.5.23.0 (for 6.5.x line) or 2025.5.0 (for cloud releases)

  1. 1. Review the Adobe Experience Manager release notes for version 6.5.23.0 (or 2025.5.0 for cloud releases) to understand changes and any migration requirements
  2. 2. Ensure you have a complete backup of your AEM instance and content repository before proceeding
  3. 3. Test the upgrade in a non-production environment first
  4. 4. Download the appropriate fixed version from Adobe's software distribution portal or through your licensed distribution channel
  5. 5. Stop the AEM instance and run the upgrade installer following Adobe's standard upgrade documentation
  6. 6. After upgrade, verify that the XSS filter configurations and Content Security Policy settings are properly configured
  7. 7. Validate that custom form components and workflows function correctly post-upgrade
  8. 8. Review and test that the stored XSS vulnerability is no longer present in form fields
Caveat Review version-specific release notes for potential breaking changes and deprecations in your custom code or integrations

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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