dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47085

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privilege authenticated users to inject malicious JavaScript into form fields. The malicious payload is persisted and executes when other users view the affected pages.

MitigationUpdate Adobe Experience Manager to a version newer than 6.5.22 per the vendor security advisory. Additionally, implement output encoding and input validation on affected form fields to prevent XSS.

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 Welcome page or use the version indicator at /system/console/bundles, or run: curl -s http://localhost:4502/crx/packmgr/service.jsp?cmd=ls 2>/dev/null | grep -i version. The version is also visible in the AEM startup log.
    Affected if The version is 6.5.22 or earlier, or 2025.4.x or earlier (i.e., less than 6.5.23.0 or less than 2025.5.0)
  2. Confirm Forms module is enabled
    Navigate to /aem/forms in the URL or check the AEM package manager at /crx/packmgr for installed form-related packages. Alternatively, check /libs/fd/fp extensions are accessible.
    Affected if Forms module is installed and accessible at standard form endpoints such as /aem/forms or /content/forms
  3. Verify low-privilege user access to form authoring
    Log in as a non-admin user (e.g., a user with 'content-author' or 'forms-user' group membership) and attempt to access the Forms console at /aem/forms or create/edit a form at /content/forms/af.
    Affected if Low-privilege authenticated users can access form creation or editing interfaces without elevated permissions
  4. Inspect form field configurations for input validation
    Review form field XML configurations under /content/forms/af or check the Granite form components at /libs/foundation/components/form. Look for fields that accept user input without explicit 'allowHTML' restrictions.
    Affected if Form fields exist that allow rich text input or have no server-side input validation rules configured

You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND the Forms module is enabled with low-privilege user access to form fields.

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

Update Adobe Experience Manager to a version newer than 6.5.22 per the vendor security advisory. Additionally, implement output encoding and input validation on affected form fields to prevent XSS.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 (for 6.5.x on-prem line) or 2025.5.0 (for 2025 cloud releases)

  1. 1. Identify the current Adobe Experience Manager version in use (check AEM welcome page or system console)
  2. 2. Determine which release line you're on: 6.5.x (on-prem) or 2025.x (cloud)
  3. 3. For 6.5.x on-prem: Plan upgrade to AEM 6.5.23.0 or later
  4. 4. For 2025 cloud releases: Plan upgrade to 2025.5.0 or later
  5. 5. Review official Adobe upgrade documentation on helpx.adobe.com for your specific version path
  6. 6. Create a full backup of the AEM instance, including repository content and configurations
  7. 7. Test the upgrade in a staging/development environment first
  8. 8. Validate that the XSS vulnerability is resolved by testing the previously affected form fields
Caveat Point releases typically have minimal breaking changes; review Adobe's release notes for any deprecation or configuration changes 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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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