dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46995

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

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged authenticated attacker can inject malicious JavaScript payloads into vulnerable form inputs, which persist on the server. When other users browse to pages containing these compromised fields, the malicious script executes in their browsers, enabling session hijacking, data theft, or defacement.

MitigationApply the vendor patch for AEM 6.5.22 or later. Additionally, implement output encoding and Content Security Policy headers as defense-in-depth measures.

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. Confirm Adobe Experience Manager is installed
    Check for AEM by accessing the admin console at /libs/granite/security/content/useradmin.html or looking for 'Adobe Experience Manager' in the web application banner. Check the startup logs or system information page at /system/console/systeminfo for AEM artifacts.
    Affected if AEM is present in the environment
  2. Determine the installed AEM version
    Navigate to the AEM Welcome page and click 'About Adobe Experience Manager' or access /system/console/systemInfo via the OSGi web console to retrieve the exact version number from the 'Product Information' section.
    Affected if The version is 6.5.22 or earlier, or the version is below 2025.5.0
  3. Verify the Forms module is enabled
    Check if the AEM Forms component is installed by navigating to /aem/forms or inspecting the OSGi bundles for 'com.adobe.aemds-*' packages in the /system/console/bundles console.
    Affected if AEM Forms modules are installed and enabled
  4. Confirm user authentication is configured
    Verify that AEM user authentication is enabled by checking for login pages at /libs/granite/core/content/login.html or by confirming the presence of user accounts in the User Administration console at /libs/granite/security/content/useradmin.html.
    Affected if User authentication is enabled and low-privileged user accounts exist in the system

A user is affected if they are running AEM version 6.5.22 or earlier (or version below 2025.5.0) with the Forms module enabled and user authentication configured, as this combination allows the stored XSS vulnerability in form fields to be exploitable.

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 for AEM 6.5.22 or later. Additionally, implement output encoding and Content Security Policy headers as defense-in-depth measures.

Recommended fix High confidence

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

  1. 1. Backup your current Adobe Experience Manager instance and database before proceeding with any upgrade.
  2. 2. Review Adobe's official upgrade documentation for AEM 6.5.23.0 or the 2025.5.0 release.
  3. 3. Download Adobe Experience Manager version 6.5.23.0 or later (for 6.5.x line) or version 2025.5.0 or later from the Adobe distribution portal.
  4. 4. Run the upgrade following Adobe's recommended upgrade procedure for your specific deployment (AEM 6.5 or Cloud Service).
  5. 5. After upgrade, verify that the stored XSS vulnerability is remediated by testing form fields that could accept user input.
  6. 6. Ensure all custom code and third-party integrations are tested for compatibility with the new version.

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