dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47036

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 vulnerability in form fields. Low-privileged attackers can inject malicious JavaScript into these fields, which executes in the browsers of users who view the affected pages.

MitigationUpgrade AEM to a version newer than 6.5.22 per Adobe's official security bulletin. Implement input validation and output encoding on form fields as a defense-in-depth measure.

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 installed AEM version
    Access the AEM Welcome page or use the system console (/system/console/bundles) to view the AEM version information. Alternatively, check the crx-quickstart/license.properties file for the productVersion field.
    Affected if The version is lower than 6.5.23.0 for 6.x releases, or lower than 2025.5.0 for newer release trains.
  2. Locate form field components in use
    Search the AEM content repository (via CRXDE Lite at /crx/de or using Query Builder) for nodes of type 'nt:unstructured' or 'cq:Component' that contain form-related resource types such as 'foundation/components/form' or custom form field components under /apps or /libs.
    Affected if Form components with editable text input fields are present in the content repository.
  3. Verify if low-privileged users have form authoring access
    Navigate to AEM Groups and Permissions (via Tools > Security > Groups or /libs/granite/security/content/useradmin) and check if standard 'content-authors' or low-privilege user groups have create, modify, or delete permissions on form content paths under /content.
    Affected if Low-privileged users (content-authors, community members, or custom low-access groups) can create or edit form field content.
  4. Inspect form field input validation settings
    Review the form component configuration dialogs (.xml or .xml.dita in /apps) for the affected form fields and check whether input validation and output encoding are explicitly disabled or missing.
    Affected if No server-side input validation pattern or output encoding rules are configured on the form field components.

Your environment is affected if AEM version is below 6.5.23.0 (or below 2025.5.0), forms with editable fields are deployed, and low-privileged users can inject or modify form field content without validation.

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 AEM to a version newer than 6.5.22 per Adobe's official security bulletin. Implement input validation and output encoding on form fields as a defense-in-depth measure.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 or later (6.5.x line); Adobe Experience Manager 2025.5.0 or later (2024+ release cycle)

  1. 1. Backup your current Adobe Experience Manager instance and database before proceeding with any upgrade.
  2. 2. Review the Adobe Experience Manager 6.5.23.0 release notes at helpx.adobe.com for any migration or compatibility requirements.
  3. 3. Ensure your system meets the minimum requirements for version 6.5.23.0 or 2025.5.0.
  4. 4. Perform a test upgrade in a non-production environment first to validate compatibility with custom code and third-party integrations.
  5. 5. Execute the upgrade following Adobe's documented upgrade procedures for your deployment type.
  6. 6. After upgrading, verify that the XSS vulnerability is remediated by testing the affected form fields.
  7. 7. Deploy the validated upgrade to production.
Caveat Review Adobe's migration guide and release notes for potential breaking changes between your current version and 6.5.23.0 - custom components, third-party integrations, or older APIs may require updates

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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