CVE-2024-26057
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 typically requires user interaction, such as convincing a user to click on a specially crafted link or to submit a form that triggers the malicious script.
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 versions 6.5.20 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript that executes in the victim's browser context by tricking users into clicking crafted links or submitting specially designed forms.
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.
-
Check AEM version in the product consoleNavigate to the AEM Welcome page and look for the version information, typically at the bottom of the screen, or access the system information console at /system/console/product, or use the CRXDE Lite welcome page which displays version detailsAffected if The displayed version is 6.5.20 or earlier, or falls below version 2024.5 (such as 2024.1 through 2024.4) - both indicate the instance is unpatched and vulnerable
-
Query version via AEM Web ConsoleAccess the Adobe Experience Manager Web Console at /system/console/status-productinfo or /crx/packmgr/service.jsp and examine the Product Version fieldAffected if The reported version number is less than 6.5.21 or less than 2024.5, meaning the DOM-based XSS patch has not been applied
-
Verify AEM service pack levelCheck the installed service packs through the Package Manager at /crx/packmgr or by reviewing the list of installed packages in the AEM System Overview at /system/overviewAffected if The cumulative service pack is numbered below 21 (for 6.5.x branches), indicating the instance is running an unpatched version
-
Identify if user-generated content handling is exposedReview any custom components or forms that accept user input, particularly those that render content without server-side output encoding - examine JSP/HTL templates for unescaped context variablesAffected if The AEM instance hosts custom components or forms that render user-supplied input without proper encoding, combined with a version in the affected range, the DOM XSS can be triggered via crafted links or forms
If your AEM installation shows version 6.5.20 or earlier, or any version below 2024.5, and you have custom components handling user input, you are likely affected by this DOM-based XSS vulnerability and should apply the vendor patch.
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 the vendor patch by upgrading AEM beyond version 6.5.20 to the latest available patched version. Additionally, implement output encoding and content security policy headers as defense-in-depth measures.
Adobe Experience Manager 6.5.21 or later, or 2024.5 or later
- 1. Identify the current Adobe Experience Manager version by checking the system information in AEM Web Console or crx/de Lite
- 2. Create a full backup of the AEM instance including the repository (crx-quickstart), database, and any custom configurations
- 3. Review the Adobe Experience Manager 6.5.21 release notes and 2024.5 release notes for any migration requirements or breaking changes specific to your instance
- 4. Test the upgrade in a non-production environment first to ensure compatibility with custom code and configurations
- 5. For AEM 6.5.x instances: Upgrade to version 6.5.21 or later by applying the latest Service Pack
- 6. For AEM as a Cloud Service or 2024.x versions: Upgrade to version 2024.5 or later through the Cloud Manager or standard upgrade process
- 7. After upgrade, verify that the DOM-based XSS vulnerability is resolved by reviewing the fixed versions' security patches
- 8. Test critical user workflows to ensure the upgrade did not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26057 — 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-26057 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