dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47088

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 in form fields. A low-privilege attacker can inject malicious JavaScript that executes in victims' browsers when they view pages containing the compromised form fields.

MitigationApply the vendor patch by updating Adobe Experience Manager to version 6.5.23 or later. Additionally, implement output encoding on form field inputs to prevent script 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. Determine installed AEM version
    Access the AEM Web Console about page at /system/console/about or check the version from the AEM Start page. Also check the package manager for com.adobe.aemforms-version information.
    Affected if The installed version is earlier than 6.5.23.0 or earlier than 2025.5.0 (the Cloud Service version).
  2. Identify if AEM Forms module is enabled
    Check the AEM Felix console at /system/console/components for Adobe Experience Manager Forms-related components, or navigate to /libs/fd/fm/view/forms/main.html in the author instance.
    Affected if AEM Forms or Adaptive Forms components are installed and enabled, as the XSS vulnerability exists in form field inputs.
  3. Check for custom form field implementations
    Review form models and templates under /apps or /libs that define form field components. Look for any custom form field components that may bypass default encoding protections.
    Affected if Custom form field components exist that do not apply output encoding to user-supplied values.
  4. Audit low-privilege user access to form editing
    Review user/group permissions in AEM at /useradmin. Check if low-privilege users (contributors, content authors) have access to create or edit form content under /content/forms.
    Affected if Low-privilege users can create or modify form fields without proper sanitization controls.

You are affected if your AEM installation is version 6.5.22 or earlier, or your AEM cloud version is earlier than 2025.5.0, and AEM Forms module is enabled allowing user-contributed form field content.

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

Apply the vendor patch by updating Adobe Experience Manager to version 6.5.23 or later. Additionally, implement output encoding on form field inputs to prevent script execution.

Recommended fix High confidence

6.5.23.0 or later 6.5.x release; alternatively 2025.5.0 or later

  1. 1. Back up your current AEM instance including the repository, configuration, and custom code.
  2. 2. Review the Adobe Experience Manager 6.5.23.0 release notes for any breaking changes or migration requirements.
  3. 3. Download Adobe Experience Manager 6.5.23.0 (or later 6.5.x release) from the Adobe Software Distribution portal.
  4. 4. Install the upgrade following Adobe's standard upgrade procedure for your deployment type.
  5. 5. After upgrade, verify that all custom form components with user input fields properly encode output to prevent XSS.
  6. 6. Test the application to confirm the stored XSS vulnerability is remediated.
Caveat Review 6.5.23.0 release notes for breaking changes specific to your deployment; minor version upgrades typically have low risk

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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