dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-43723

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 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 attackers can inject malicious scripts through manipulated DOM elements via crafted URLs or user input. The malicious payload executes when the affected page renders in the victim's browser, allowing arbitrary code execution in the context of the victim's session.

MitigationUpgrade to Adobe Experience Manager 6.5.22 or later to obtain the vendor patch. Additionally, implement Content Security Policy (CSP) headers and validate/sanitize all user-supplied input and URL parameters before DOM manipulation.

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. Identify installed AEM version
    Access the AEM System Information console at /system/console/status/productinfo or check the version file in the installation directory. Alternatively, run: curl -s http://localhost:4502/crx/packmgr/service.jsp?cmd=version
    Affected if The version shown is 6.5.21 or earlier, or falls below 2024.11.0
  2. Confirm AEM release track
    In the AEM console, navigate to Help > About Adobe Experience Manager to determine if you are on the 6.5.x LTS track or the monthly release track (2024.x)
    Affected if Running 6.5.x LTS version 6.5.21 or earlier, or running any 2024 monthly release prior to November 2024
  3. Inspect Content Security Policy headers
    Use browser dev tools or run: curl -sI http://localhost:4502/ | grep -i content-security-policy. Also check in AEM OSGi config: com.adobe.granite.security.policy.header
    Affected if No CSP headers are configured, or CSP allows unsafe-inline scripts
  4. Review custom components for DOM manipulation
    Search the codebase for JavaScript files containing innerHTML, outerHTML, document.write, or similar DOM sinks that use URL parameters or user input without sanitization. Check in /apps for custom components handling request parameters
    Affected if Custom components exist that pass unsanitized request parameters or user input directly to DOM manipulation methods
  5. Audit sling request parameters usage
    Search for usage of request.getParameter(), slingRequest.getParameter(), or similar in JSP/HTL scripts under /apps. Look for patterns where these values are rendered without encoding
    Affected if Request parameters are used in templates or components without proper XSS protection (use of encodeForHTML or similar)
  6. Check publish instance exposure
    Verify if the AEM publish instance is accessible externally without authentication. Run: curl -s http://publish-host:4503/ and inspect if custom error handlers or static resources reflect URL input
    Affected if Publish instances are externally accessible and custom error pages or static resources reflect URL parameters in the response

You are affected if your AEM version is 6.5.21 or earlier on the 6.5.x LTS track, or any version below 2024.11.0 on the monthly release track, and your environment either lacks CSP headers or contains custom components that manipulate the DOM with unsanitized user input or URL parameters.

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 Adobe Experience Manager 6.5.22 or later to obtain the vendor patch. Additionally, implement Content Security Policy (CSP) headers and validate/sanitize all user-supplied input and URL parameters before DOM manipulation.

Recommended fix High confidence

Adobe Experience Manager 6.5.22.0 or later (for on-premise); Adobe Experience Manager Cloud Service 2024.11.0 or later

  1. Review Adobe Experience Manager 6.5.22.0 release notes for new features, bug fixes, and any known issues before upgrading
  2. Ensure your current AEM instance meets the prerequisites for upgrading to 6.5.22.0
  3. Perform a full backup of your AEM repository, database, and configuration files
  4. Test the upgrade in a staging or development environment before applying to production
  5. Stop the AEM instance and any related services
  6. Run the AEM upgrade procedure according to Adobe's official upgrade documentation (typically using the Upgrade Procedure or CRX Package Manager)
  7. After upgrade, verify that all custom applications, workflows, and integrations function correctly
  8. Validate that the DOM-based XSS vulnerability is remediated by testing the affected vectors
Caveat Upgrading AEM within the same major version (6.5.x) typically has low risk, but custom code, third-party integrations, and older APIs may require testing and potential adjustments

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
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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