dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-43735

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 reflected Cross-Site Scripting (XSS) vulnerability. If an attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser.

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 · moderate confidence

Adobe Experience Manager versions 6.5.21 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability where malicious JavaScript can be injected via URLs referencing vulnerable pages. The attack requires social engineering to convince victims to click specially crafted URLs, after which the malicious payload executes within the victim's browser context.

MitigationApply the vendor patch when available; in the interim, implement WAF rules to detect and block XSS patterns in URL parameters, and educate users about avoiding untrusted links.

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 AEM product version
    Access the AEM Web Console (Help > System Information) or check the version.properties file in the crx-quickstart folder. You can also query the /system/console/status-productinfo endpoint.
    Affected if The reported version is below 6.5.22.0 or below 2024.11.0
  2. Confirm AEM edition and deployment type
    Verify that the instance is Adobe Experience Manager (not Adobe Campaign, Adobe Target, or other Adobe products). Check the product name in the AEM Welcome page or system console.
    Affected if The product is confirmed as Adobe Experience Manager and the version from step 1 falls in the affected range
  3. Review URL parameter handling in custom components
    Inspect any custom AEM components, Sling models, or servlets that process URL parameters (query strings, path variables). Look for cases where URL input is reflected directly in HTML output without proper encoding.
    Affected if Custom code reads URL parameters and outputs them to pages without contextual encoding (for example, using request parameters in response.write or direct JSP/Servlet output)
  4. Check for existing XSS filtering configurations
    Examine the OSGi configuration for XSS protection (com.adobe.granite.xss) and any custom request filters. Look at the XSSAPI.isValidURL or isValidHTML methods used in your templates.
    Affected if No XSS filtering is applied to URL parameters, or the filtering is disabled/misconfigured

You are affected if your AEM version is below 6.5.22.0 (for 6.5.x releases) or below 2024.11.0 (for 2024 releases) and your application reflects URL parameters in responses without proper sanitization.

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

Apply the vendor patch when available; in the interim, implement WAF rules to detect and block XSS patterns in URL parameters, and educate users about avoiding untrusted links.

Recommended fix High confidence

Adobe Experience Manager 6.5.22.0 or later; AEM as a Cloud Service 2024.11.0 or later

  1. 1. Identify your current Adobe Experience Manager version to confirm it is affected (6.5.21 or earlier, or before 2024.11.0 for Cloud Service).
  2. 2. For AEM 6.5 on-premises: Upgrade to Adobe Experience Manager version 6.5.22.0 or later.
  3. 3. For AEM as a Cloud Service: Upgrade to version 2024.11.0 or later.
  4. 4. After upgrading, verify the XSS vulnerability is resolved by testing the affected endpoint.
  5. 5. Consider performing a full regression test suite to ensure the upgrade does not break existing functionality.
Caveat Standard upgrade risks apply - review Adobe's release notes for 6.5.22.0 and 2024.11.0 for any compatibility or configuration changes before deploying to production

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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