dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26105

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 6.5.20.0 / 2024.3.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.19 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 · high confidence

Adobe Experience Manager versions 6.5.19 and earlier contain a reflected XSS vulnerability where malicious JavaScript can be injected into URL parameters. When a victim is tricked into visiting a crafted URL, the server reflects the unsanitized input back in the HTTP response, causing the malicious script to execute within the victim's browser context.

MitigationApply the AEM security patch (version 6.5.20 or later) to address the vulnerability. Additionally, implement input validation, output encoding, and Content Security Policy headers as defense-in-depth measures.

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.20.0< 2024.3.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 Adobe Experience Manager version
    Access the AEM system information console at /system/console/status or check the version.properties file in the crx-quickstart directory. The version is typically displayed as a numerical release like 6.5.x or a date-based release like 2024.x
    Affected if The installed version is below 6.5.20.0 or below 2024.3.0
  2. Identify URL parameter reflection points
    Review web application logs and proxy traces to identify which AEM endpoints accept user-supplied URL parameters and reflect them unencoded in HTTP responses. Common paths include content and commerce-related selectors.
    Affected if Any AEM endpoint reflects URL parameter values directly in the response body without sanitization
  3. Verify if vulnerable endpoints are exposed
    Test suspected parameter-handling endpoints by injecting a benign payload like <script>alert(1)</script> into URL query parameters and examining whether the payload appears unescaped in the response.
    Affected if The test payload is reflected verbatim in the page output rather than being HTML-encoded
  4. Check for Content Security Policy headers
    Inspect HTTP response headers from AEM pages to determine if Content-Security-Policy headers are configured and enforced.
    Affected if No CSP headers are present, or CSP headers allow inline scripts, which would enable XSS execution
  5. Review input validation configuration
    Examine AEM's sling:ignoreUrlParams or custom input validation filters in the OSGi configuration console at /system/console/configMgr.
    Affected if No input validation or output encoding filters are configured for the affected URL parameter handling

You are affected if your AEM version is below 6.5.20.0 or below 2024.3.0 AND your application reflects URL parameters in responses without 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.20.0 / 2024.3.0 or later
Fixed in 6.5.20.02024.3.0
Interim mitigation

Apply the AEM security patch (version 6.5.20 or later) to address the vulnerability. Additionally, implement input validation, output encoding, and Content Security Policy headers as defense-in-depth measures.

Recommended fix High confidence

Adobe Experience Manager 6.5.20.0 (for 6.5.x branch) or 2024.3.0 (for 2024.x branch)

  1. 1. Identify the current Adobe Experience Manager version in use
  2. 2. Create a full backup of the AEM repository (including content and configurations)
  3. 3. Test the upgrade in a staging environment before applying to production
  4. 4. For AEM 6.5.x line: upgrade to version 6.5.20.0 or later
  5. 5. For AEM 2024.x line: upgrade to version 2024.3.0 or later
  6. 6. After upgrade, verify that the XSS vulnerability is resolved by testing the previously vulnerable endpoint
  7. 7. Validate that custom code and third-party integrations remain functional
Caveat AEM upgrades may introduce compatibility issues with custom components or third-party integrations; thoroughly test in non-production environment before deploying

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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