CVE-2024-26053
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 · uneditedAdobe Experience Manager versions 6.5.20 and earlier Answer: are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. This vulnerability could allow an attacker to execute arbitrary JavaScript code in the context of the victim's browser session. Exploitation of this issue requires user interaction, such as convincing a victim to click on a specially crafted link or to submit a form that triggers the vulnerability.
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 confidenceAdobe Experience Manager 6.5.20 and earlier versions contain a DOM-based Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript through specially crafted links or form submissions, which executes in the context of the victim's browser session. This requires user interaction such as clicking a malicious link or submitting a crafted form.
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< 6.5.21< 2024.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed AEM 6.5.x version numberAccess the AEM Welcome page (typically at /libs/granite/core/content/login.html or /aem/start.html) and locate the version displayed in the footer, or check the version.properties file in the AEM installation directory under crx-quickstart/confAffected if The displayed version is 6.5.20 or any version earlier than 6.5.21
-
Identify the installed AEM 2024.x version numberAccess the AEM Welcome page or check the version.properties file as above, looking for the 2024.x year-based version numberingAffected if The displayed version shows a 2024.x release that is earlier than 2024.5
-
Verify web-based author or publish instance is accessibleConfirm that HTTP/HTTPS access to the AEM instance is enabled by attempting to reach the login page or any published content endpointAffected if The instance is reachable over the network and accepts user connections, which would allow the XSS attack vector through malicious links or form submissions
Your environment is affected if the installed Adobe Experience Manager version is 6.5.20 or earlier, or any 2024.x version prior to 2024.5, and the web interface is accessible to users who could click malicious links or submit crafted forms.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.212024.5
Apply Adobe Experience Manager service pack 6.5.21 or later, which contains the security patch for this DOM-based XSS vulnerability.
Adobe Experience Manager 6.5.21 (on-premise) or 2024.5 (Cloud Service)
- 1. Identify your Adobe Experience Manager deployment type (AEM 6.5 on-premise or AEM as a Cloud Service)
- 2. For AEM 6.5.x on-premise: Upgrade to version 6.5.21 or later from the Adobe Software Distribution portal
- 3. For AEM as a Cloud Service: Ensure your environment is updated to the 2024.5 release or later through the Cloud Manager
- 4. After upgrade, verify the XSS fix is applied by testing with a benign payload in affected input fields
- 5. Clear browser cache and test in non-production environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-26053 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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