dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47038

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 · moderate confidence

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript payloads into vulnerable input fields, which are then stored and executed in victim users' browsers when they view the affected page.

MitigationUpgrade to a patched version of Adobe Experience Manager (if available) and implement output encoding/input validation on all form field components to prevent 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 the installed AEM version
    Navigate to the AEM welcome page or check the version via the system information console (typically at /system/console/bundles or /crx/packmgr/service.jsp), or run: 'java -jar aem-author.jar -v' if you have access to the startup script. Look for the version number in the output.
    Affected if The version is lower than 6.5.23.0 (for 6.5.x releases) or lower than 2025.5.0 (for Cloud/2025 releases).
  2. Determine if Core Components with Forms are deployed
    Check the package manager (/crx/packmgr/index.jsp) for installed form-related packages such as 'core-wcm-components' or 'core-forms-components'. Inspect the /apps folder for the presence of form components under /libs/fd/af/components or custom form implementations.
    Affected if Form components are installed and actively used in your content pages.
  3. Verify low-privileged user access to form authoring
    Review the permissions for standard users (non-admin) in the user admin console (/security/users.html) or group permissions. Check if content authors with 'contributor' or 'author' roles can create or edit pages containing form components.
    Affected if Low-privileged users (contributors, authors) have create or edit permissions on pages that render form fields.
  4. Inspect existing form content for unencoded payloads
    Use the AEM Query Builder API (e.g., /bin/querybuilder.json?type=nt:unstructured&property=jcr:title or search for form-related content nodes under /content) or navigate to known form pages and inspect the HTML source of submitted form data stored in the repository under /content/forms/af/.
    Affected if Stored form data contains raw HTML script tags or JavaScript event handlers (onerror, onload, etc.) that appear unescaped in the page source.

Your environment is affected if you are running AEM versions below 6.5.23.0 or below 2025.5.0 and your instance allows low-privileged users to create or edit content in form fields that are rendered without proper output 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 to a patched version of Adobe Experience Manager (if available) and implement output encoding/input validation on all form field components to prevent XSS execution.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 (LTS) or Adobe Experience Manager 2025.5.0 (or later)

  1. Verify the current Adobe Experience Manager version by checking the system console or version.properties file
  2. Determine which release train you are on (6.5.x LTS or 2024.x/2025.x)
  3. For 6.5.x LTS users: Schedule maintenance window and backup the AEM instance
  4. Download Adobe Experience Manager 6.5.23.0 or later from the Adobe Software Distribution portal
  5. Deploy the upgrade following Adobe's standard upgrade documentation for your deployment pattern (in-place or rolling upgrade)
  6. After upgrade, verify the AEM version shows 6.5.23.0 or later in the system console
  7. For 2024.x/2025.x users: Download and deploy Adobe Experience Manager 2025.5.0 or later
  8. Test that the affected form fields now properly sanitize input to prevent XSS

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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