dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-48264

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 6.5.25.0 / 2026.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.24, LTS SP1, 2026.04 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. An attacker could exploit this issue by manipulating the DOM environment to execute malicious JavaScript within the context of the victim's browser. Exploitation of this issue requires user interaction in that a victim must visit a crafted webpage. Scope is changed.

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 is affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. The vulnerability allows attackers to manipulate the DOM environment through malicious input, causing the victim's browser to execute arbitrary JavaScript in the context of the affected AEM application. This is a client-side vulnerability where the attack payload is processed by JavaScript code without proper sanitization.

MitigationApply the vendor patch for AEM versions 6.5.24, LTS SP1, and 2026.04 once released. In the interim, implement strict Content Security Policy (CSP) headers and sanitize all user-controlled input before DOM manipulation.

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.25.0< 2026.5.0= 6.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. Identify installed AEM version
    Access the AEM Web Console (typically at /system/console/config) or check the/crx/packmgr/service.jsp endpoint. You can also find the version in the about.json file at /libs/granite/core/content/login.json or through the AEM Welcome page under Version Information.
    Affected if The installed version is 6.5.24, 6.5 (LTS SP1), 2026.04, or any version earlier than 6.5.25.0 or 2026.5.0
  2. Confirm AEM 6.5 LTS release
    Check the product version details through the AEM About page (Help > About Adobe Experience Manager) or via the version.properties file in the installation directory.
    Affected if The version is listed as 6.5 without a service pack number indicating 6.5.25.0 or later
  3. Review custom client-side code for DOM manipulation
    Examine any custom HTL (HTML Template Language) templates, clientlibs JavaScript files, and前端 components that use document.write(), innerHTML, outerHTML, or similar DOM manipulation methods. Search for user input being directly inserted into the DOM without sanitization.
    Affected if Custom client-side code directly manipulates the DOM with unsanitized user input or URL parameters
  4. Check for Content Security Policy (CSP) headers
    Inspect the HTTP response headers on your AEM publish and author instances. Look for CSP header configuration in the Apache Sling header filtering or dispatcher configuration files.
    Affected if No CSP headers are configured, or CSP allows unsafe-inline scripts that could permit DOM XSS execution

You are affected if your AEM version is before 6.5.25.0 (for 6.5.x branches) or before 2026.5.0 (for 2026.x branches), and your application uses client-side code that manipulates the DOM without proper sanitization.

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.25.0 / 2026.5.0 or later
Fixed in 6.5.25.02026.5.0
Interim mitigation

Apply the vendor patch for AEM versions 6.5.24, LTS SP1, and 2026.04 once released. In the interim, implement strict Content Security Policy (CSP) headers and sanitize all user-controlled input before DOM manipulation.

Recommended fix High confidence

AEM 6.5.25.0 (LTS) or AEM 2026.5.0 (latest release train)

  1. Upgrade AEM 6.5.x instances to version 6.5.25.0 or later
  2. If running on the 2026.x release train, upgrade to 2026.5.0 or later
  3. After upgrading, verify the fix by testing the affected DOM manipulation scenarios
  4. Consult Adobe's official upgrade documentation for your specific AEM deployment type before proceeding
Caveat Review Adobe's release notes for 6.5.25.0 for any compatibility or migration considerations specific to your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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