CVE-2024-43724
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.21 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability that could be exploited by an attacker to execute arbitrary code in the context of the victim's browser session. By manipulating a DOM element through a crafted URL or user input, the attacker can inject malicious scripts that run when the page is rendered. Exploitation of this issue requires user interaction.
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.21 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where attackers can inject malicious scripts into DOM elements via crafted URLs or user input. When the page renders, the injected script executes in the victim's browser context, enabling session hijacking or arbitrary code 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< 6.5.22.0< 2024.11.0CVSS 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 installed Adobe Experience Manager versionNavigate to the AEM Welcome page or check the version.properties file in the crx-quickstart folder. On the AEM welcome page, look for the version number displayed in the product information section.Affected if The installed version is earlier than 6.5.22.0 or earlier than the November 2024 release (2024.11.0). Compare your exact version number against these thresholds.
-
Identify AEM release train versionAccess the AEM System Information console at /system/console/configMgr or check the version info via the AEM Web Console. Locate the product version information to determine if it follows the 6.5.x train or the year-based 2024.x train.Affected if The release train version is below 6.5.22.0 for the 6.5 train, or below 2024.11.0 for the year-based release train.
-
Verify Content Security Policy configurationCheck the Apache Sling Header filter configuration or dispatcher configuration for CSP response headers. Inspect the HTTP responses from your AEM instance using browser developer tools or curl -I to examine response headers.Affected if No Content-Security-Policy header is set, or CSP headers are not configured to restrict inline scripts, which would allow injected scripts to execute.
-
Review URL parameter handlingAudit custom components, servlet filters, or client-side JavaScript that processes URL parameters (query strings) and renders them into the page DOM without sanitization. Check clientlibs and custom JS files for direct use of location.search or similar APIs.Affected if Custom or core AEM components process URL parameters and insert them directly into the DOM without applying proper encoding or sanitization.
You are affected if your AEM version is below 6.5.22.0 or below 2024.11.0, and your instance processes URL parameters or user input into DOM elements without sanitization or CSP protection.
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.22.02024.11.0
Upgrade Adobe Experience Manager to version 6.5.22 or later. Additionally, implement Content Security Policy (CSP) headers and validate/sanitize all user inputs and URL parameters to prevent DOM manipulation attacks.
6.5.22.0 (LTS) or 2024.11.0 (Feature Release)
- 1. Identify the current Adobe Experience Manager version in use by checking the system information or AEM version file
- 2. Determine which release train the instance follows (6.5.x LTS or 2024.x feature release)
- 3. For 6.5.x LTS users: Plan upgrade to version 6.5.22.0 or later
- 4. For 2024.x users: Plan upgrade to version 2024.11.0 or later
- 5. Review Adobe's upgrade documentation and release notes for the target version
- 6. Perform a full backup of the AEM instance and content repository before upgrading
- 7. Test the upgrade in a non-production environment first
- 8. Schedule maintenance window and execute the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43724 — 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-43724 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