CVE-2024-49524
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 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. This type of attack requires user interaction, as the victim would need to access a manipulated URL or provide specific input to trigger 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 versions 6.5.20 and earlier contain a DOM-based Cross-Site Scripting vulnerability where malicious scripts can be injected through manipulated URLs or user input that gets rendered in the browser's DOM without proper sanitization. Attackers exploit this by tricking users into accessing crafted URLs or providing specific input that triggers script execution when the page renders.
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.0< 2024.5.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.
-
Identify installed AEM versionAccess the AEM Welcome page or check the product version through the system console at /system/console/productinfo. Alternatively, locate the version file in the installation directory or check via command line using the AEM version command.Affected if The installed version is AEM 6.5.20 or earlier, or any version below 2024.5.0
-
Verify version against fixed releasesCompare your identified version to the fixed releases: AEM 6.5.21.0 and 2024.5.0. If your version is below both of these thresholds, your environment falls within the affected range.Affected if Your version is below 6.5.21.0 for the 6.5.x branch OR below 2024.5.0 for the newer release line
-
Check for unpatched AEM instances in a clusterIf running AEM in a clustered or publish-farm setup, verify the version on all primary and publish instances. Use the Web Console on each instance at /system/console/bundles or check version via the CRXDE Lite welcome page.Affected if Any instance in the cluster runs an affected version (6.5.20 or earlier, or below 2024.5.0)
-
Review custom code handling user inputAudit any custom components, servlets, or Experience Fragments that render URL parameters or form input directly into HTML output without encoding. Search codebase for direct output of request parameters (request.getParameter) that gets written to response.Affected if Custom code renders user-supplied input directly into the DOM without proper output encoding, and the AEM version is within the affected range
Your environment is affected if AEM is running version 6.5.20 or earlier, or any version below 2024.5.0, AND the application renders user-supplied input or URL parameters in the browser DOM without sanitization.
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.21.02024.5.0
Implement output encoding and input validation for all user-supplied data rendered in the DOM, and apply Content Security Policy headers to restrict script execution. Upgrade to AEM 6.5.21 or later if a patched version is available.
6.5.21.0 (for 6.5.x branch) or 2024.5.0 (for 2024.x branch) or later
- 1. Identify the current Adobe Experience Manager version in use
- 2. Determine which release branch is in use (6.5.x or 2024.x)
- 3. For 6.5.x branch: Plan upgrade to version 6.5.21.0 or later
- 4. For 2024.x branch: Plan upgrade to version 2024.5.0 or later
- 5. Review Adobe's official upgrade documentation for detailed migration steps
- 6. Perform upgrade in a non-production environment first
- 7. Validate all custom code and integrations work correctly post-upgrade
- 8. Apply the upgrade to production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49524 — 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-49524 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