dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47061

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-24
Fix available
A fix is available. Upgrade to 6.5.23.0 / 2025.5 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-privileged attacker can inject malicious JavaScript scripts into vulnerable form inputs, which are then stored and executed in the browsers of users who view the affected page.

MitigationApply the vendor patch when available. In the interim, implement Content Security Policy (CSP) headers and validate/sanitize all user inputs in form fields server-side before storage and output encoding before rendering.

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

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 AEM version
    Access the AEM System Information console at /system/console/status-html or check the version file in the crx-quickstart folder. Compare the installed version against 6.5.23.0 for 6.x releases or 2025.5 for cloud releases.
    Affected if Installed version is below 6.5.23.0 for AEM 6.x or below 2025.5 for AEM as a Cloud Service.
  2. Identify form field usage
    Review the AEM content structure under /content or /apps to locate any custom form components, Adaptive Forms, or core form components that accept user input.
    Affected if Custom or out-of-the-box form components that accept and store user input are present in the environment.
  3. Verify input validation on form components
    Inspect the server-side code (Java/OSGi services) handling form submissions in /apps or /libs. Check whether form field components implement server-side validation or sanitization before storing data.
    Affected if Form components lack server-side input validation, sanitization, or output encoding.
  4. Examine stored form data for malicious scripts
    Query the JCR repository or examine form submission data in the crx/de console under /content/dam/formsanddocuments or similar data storage paths. Look for script tags, javascript: URLs, or event handlers in stored field values.
    Affected if Stored form data contains unsanitized HTML, script tags, or JavaScript event handlers.

The environment is affected if running AEM below version 6.5.23.0 or below 2025.5 and form fields with user input are present without proper server-side input validation or 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 or later
Fixed in 6.5.23.02025.5
Interim mitigation

Apply the vendor patch when available. In the interim, implement Content Security Policy (CSP) headers and validate/sanitize all user inputs in form fields server-side before storage and output encoding before rendering.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 or later (6.5.x track); Adobe Experience Manager 2025.5 or later (2025.x track)

  1. Back up the current Adobe Experience Manager instance, including repository content and configuration files
  2. Review the Adobe Experience Manager 6.5.23.0 (or 2025.5) release notes for any changes relevant to your implementation
  3. Test the upgrade in a non-production/staging environment before deploying to production
  4. Apply the upgrade to AEM following Adobe's official upgrade documentation (typically via the CRX Package Manager or new installation with content migration)
  5. After upgrade, verify the vulnerability is resolved by attempting to inject script content into the affected form fields
Caveat Review 6.5.23.0 release notes for any compatibility or deprecation notices; security patch releases typically have minimal breaking changes but test thoroughly

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