dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-48262

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to after 2020.5.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 5 weeks old

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 is 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

DOM-based Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager where malicious JavaScript can be executed via manipulation of the DOM environment. The vulnerability requires user interaction (victim visiting a crafted webpage) and has a changed scope, indicating the attack can access resources outside the victim's origin.

MitigationImplement proper output encoding and sanitization for all data inserted into the DOM; utilize safe DOM APIs that automatically escape content, and implement Content Security Policy (CSP) headers to mitigate XSS execution.

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<= 2020.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 Adobe Experience Manager version
    Access the AEM Web Console (typically at /system/console/configMgr) or check the version.properties file in the crx-quickstart folder. Alternatively, access the AEM welcome page which displays the version number.
    Affected if The installed version is 6.5.25.0 or lower, or 2020.5.0 or lower, or exactly 6.5 (any 6.5.x variant).
  2. Identify custom frontend components handling DOM manipulation
    Review custom OSGi bundles or client-side JavaScript files in /apps for code that uses innerHTML, outerHTML, document.write, or similar DOM-manipulation APIs without proper encoding.
    Affected if Custom or third-party components that insert unsanitized user input into the DOM are deployed.
  3. Audit JavaScript code for DOM sinks
    Search the codebase (especially in /apps and /libs) for JavaScript files containing dangerous DOM sinks such as innerHTML, outerHTML, insertAdjacentHTML, eval(), or document.write().
    Affected if Any JavaScript code path uses these sinks with data that could originate from URL parameters, user input, or external sources without sanitization.
  4. Identify endpoints accepting user input that feed into DOM operations
    Review AEM component templates and HTL scripts for data-binding expressions that render user-controlled content, particularly in custom components or third-party packages.
    Affected if Components render user-submitted or URL-derived content directly into HTML without encoding.

You are affected if your AEM version falls within <= 6.5.25.0, <= 2020.5.0, or = 6.5 AND your instance has custom components or code that manipulates the DOM with unsanitized user input.

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 a release after 2020.5.0
Interim mitigation

Implement proper output encoding and sanitization for all data inserted into the DOM; utilize safe DOM APIs that automatically escape content, and implement Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix Moderate confidence

AEM 6.5.26.0 or later; AEM as a Cloud Service 2020.6.0 or later

  1. 1. Identify the current Adobe Experience Manager version by checking the AEM welcome page or system console.
  2. 2. For AEM 6.5.x installations: Upgrade to AEM 6.5.26.0 or later to resolve the DOM-based XSS vulnerability.
  3. 3. For AEM as a Cloud Service (2020.x): Upgrade to version 2020.6.0 or later.
  4. 4. After upgrading, clear the AEM cache and publish the changes to all relevant instances.
  5. 5. Verify the fix by testing that the XSS vulnerability is no longer exploitable in the DOM environment.
  6. 6. Ensure all custom code and third-party integrations are tested post-upgrade for compatibility.
Caveat Standard upgrade risks apply - review Adobe's release notes for 6.5.26+ for any compatibility changes or deprecated features before upgrading production environments

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