dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46988

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

A stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged authenticated users to inject malicious JavaScript into form fields. When other users view pages containing these compromised fields, the malicious script executes in their browsers, potentially enabling session hijacking or credential theft.

MitigationUpgrade Adobe Experience Manager to version 6.5.23 or later. Additionally, implement strict input validation and output encoding on all 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. Identify installed AEM version
    Access the AEM System Information console at /system/console/status-html or check the crx-quickstart/package.properties file for the product version. Alternatively, query the JCR using a repository browsing tool to find the version property.
    Affected if The version is below 6.5.23.0 or below 2025.5.0
  2. Confirm AEM Forms module is in use
    Check if the AEM Forms add-on or Adaptive Forms feature is installed and enabled. This can be done by reviewing installed packages in the Package Manager or checking for form-related content structures in the /content/forms folder in the repository.
    Affected if Forms functionality is present and accessible to low-privileged users
  3. Audit form field content for malicious scripts
    Query the repository for stored form submissions or Adaptive Form data in the /content/forms folder and related content paths. Inspect form field values for script tags, javascript: URLs, or event handler attributes like onload, onerror, or onmouseover.
    Affected if Any form fields contain unsanitized script tags or event handler attributes that could execute in other users browsers
  4. Review recent user submissions for XSS payloads
    Check form submission logs and audit trails for entries containing common XSS patterns such as <script>, <img src=x onerror=>, or javascript: prefixes in text fields.
    Affected if Recent submissions contain suspicious patterns that may indicate exploitation attempts

You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 and your environment uses AEM Forms with user-submittable fields where input validation is not enforced.

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 Adobe Experience Manager to version 6.5.23 or later. Additionally, implement strict input validation and output encoding on all form fields as a defense-in-depth measure.

Recommended fix High confidence

AEM 6.5.23.0 (for 6.5.x line) or 2025.5.0 (for 2025 release train)

  1. Identify the current Adobe Experience Manager version by checking the AEM Welcome page or system console
  2. Determine which release line you're on: AEM 6.5.x or the 2025.x release train
  3. For AEM 6.5.x users: Plan upgrade to version 6.5.23.0 or later
  4. For 2025.x users: Plan upgrade to version 2025.5.0 or later
  5. Review Adobe's official upgrade documentation for your specific version path
  6. Back up the AEM repository (Oak repository) and database before upgrading
  7. Test the upgrade in a staging environment before production deployment
  8. Execute the upgrade following Adobe's recommended upgrade procedure
Caveat Review Adobe's release notes for your target version to identify any compatibility changes or deprecated features that may affect your custom code or integrations

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 / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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