dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47012

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into vulnerable form fields. The malicious payload persists in the system and executes in victim browsers when they navigate to pages containing the affected form fields.

MitigationApply the vendor patch (Adobe Experience Manager 6.5.23 or later) to address the vulnerability. Additionally, implement output encoding and input validation 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. Check AEM version
    Access the AEM Web Console (system/console/about) or check the version.properties file in the crx-quickstart folder to determine the installed Adobe Experience Manager version number
    Affected if The installed version is below 6.5.23.0 or below 2025.5.0
  2. Verify Forms module is in use
    Navigate to the AEM Forms interface or check for the presence of adaptive forms or form content nodes in the repository under /content/forms
    Affected if Forms or adaptive forms are created and active in the AEM environment
  3. Inspect form field configuration
    Review the XML configuration or JSON structure of adaptive form fields in the repository (under /content/forms/af) to check if input validation and output encoding are explicitly defined for each form field
    Affected if Form fields lack input validation constraints or output encoding settings configured in the form definition
  4. Identify stored form submissions
    Check the AEM Forms data store orcrx/de repository for saved form submissions that may contain unsanitized user input in form field nodes
    Affected if Form submission data nodes contain raw, unescaped HTML or script tags in field values

A user is affected if their AEM installation is version 6.5.22 or earlier (or below 2025.5.0) AND they have forms enabled with fields that lack proper input validation and output encoding, allowing stored XSS payloads to persist and execute in other users browsers.

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 (Adobe Experience Manager 6.5.23 or later) to address the vulnerability. Additionally, implement output encoding and input validation 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 (cloud/2025 line)

  1. Verify current Adobe Experience Manager version by navigating to /crx/packmgr/version.jsp or checking the about page
  2. Download Adobe Experience Manager 6.5.23.0 (or later for 6.5.x line) or 2025.5.0 (or later for cloud/2025 line) from the official Adobe distribution portal or Software Distribution
  3. Review the Adobe Experience Manager upgrade documentation for your specific version path
  4. Create a complete backup of the current AEM instance including repository, database, and configuration files
  5. Stop the AEM instance before applying the upgrade
  6. Install the new version following Adobe's standard upgrade procedures
  7. After installation, verify the upgrade was successful by checking the version number
  8. Clear browser cache and test the application to confirm the fix resolves the XSS vulnerability

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-47012 — 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-47012 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