dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-43714

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to 6.5.22.0 / 2024.11.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 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. This type of attack requires user interaction, as the victim would need to visit a malicious link or input data into a vulnerable page.

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 confidence

Adobe Experience Manager versions 6.5.21 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where malicious scripts can be injected through manipulated DOM elements via crafted URLs or user input, executing in the victim's browser session when the page renders.

MitigationUpgrade to AEM 6.5.22 or later if available; otherwise, implement output encoding and input validation for DOM manipulations, and consider Content Security Policy 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.22.0< 2024.11.0

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. Check installed AEM version
    Access the AEM Web Console Status page at /system/console/status-productinfo or check the version.properties file in the crx-quickstart folder. For AEM as a Cloud Service, check the version in Cloud Manager or the environment details.
    Affected if The installed version is older than 6.5.22.0 or older than the 2024.11.0 release.
  2. Identify custom components with DOM manipulation
    Review custom OSGi components,Sightly/JSP templates, and client-side JavaScript for usage of innerHTML, outerHTML, document.write(), or similar DOM injection methods that might process URL parameters or user-provided data.
    Affected if Custom code uses unsafe DOM manipulation methods without proper output encoding or sanitization.
  3. Audit URL parameter handling in custom code
    Search the codebase for getParameter(), request.getParameter() or similar calls that feed into DOM operations, particularly in client-side JavaScript files under /apps or /libs.
    Affected if URL parameters are directly inserted into the DOM without encoding or validation.
  4. Review form and input handling components
    Examine Experience Manager forms, dialogs, and content fragments that accept user input and render it back in the page, checking for unencoded output in the response.
    Affected if User input is rendered back in pages without proper HTML encoding or sanitization.
  5. Check for vulnerable third-party AEM components
    Review any installed third-party packages or ACS AEM Commons features that may include DOM manipulation logic, and verify they are updated to versions compatible with AEM 6.5.22+ or the 2024.11.0 release.
    Affected if Third-party components with known XSS vulnerabilities are installed and active.

You are affected if your AEM installation version is below 6.5.22.0 or below the 2024.11.0 release, and your instance runs custom or third-party code that performs unsafe DOM manipulation with user-supplied 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 6.5.22.0 / 2024.11.0 or later
Fixed in 6.5.22.02024.11.0
Interim mitigation

Upgrade to AEM 6.5.22 or later if available; otherwise, implement output encoding and input validation for DOM manipulations, and consider Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

AEM 6.5.22.0 or later for on-premise; AEM Cloud Service 2024.11.0 or later

  1. Identify your current AEM deployment type (6.5.x on-premise or AEM Cloud Service)
  2. For AEM 6.5.x on-premise: Upgrade to version 6.5.22.0 or later
  3. For AEM Cloud Service: Upgrade to version 2024.11.0 or later
  4. After upgrading, verify the DOM-based XSS vulnerability is resolved by testing the previously vulnerable URL patterns
  5. Ensure any custom code that manipulates DOM elements follows secure coding practices to prevent future XSS issues
Caveat Standard AEM minor version upgrades typically include cumulative fixes but review the specific release notes for any behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43714 — 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-2024-43714 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