dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-41847

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-23
Fix available
A fix is available. Upgrade to 6.5.21 / 2024.5 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.20 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.20 and earlier are affected by a reflected Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript into URL parameters that get reflected back and executed in victim's browsers when convinced to visit a crafted link.

MitigationUpdate Adobe Experience Manager to version 6.5.21 or later to obtain the vendor patch. Additionally, implement output encoding and input validation on vulnerable endpoints as a defense-in-depth measure while planning the update.

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.21< 2024.5

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
    Navigate to the AEM Welcome page (typically at /aem/start.html) and locate the version information in the 'Version' field, or access the System Overview console at /system/console/status-html/dochead?branch=0&ran=0&
    Affected if Version displayed is 6.5.20 or earlier, or version string contains a build number earlier than 2024.05
  2. Verify AEM version via CRXDE Lite
    Access the CRXDE Lite interface (usually at /crx/de/index.jsp) and inspect the build information in the repository, or query the version.properties file in the installation directory if accessible
    Affected if The version file shows a release older than 6.5.21 or the 2024.5 release branch
  3. Identify exposed endpoints with parameter reflection
    Review commonly affected AEM endpoints that handle URL parameters and return them in responses, including /libs/granite/core/content/login.html, search handlers, and custom servlet endpoints that do not use proper output encoding
    Affected if URL parameters are returned in HTML responses without encoding and the AEM version is within the affected range
  4. Audit recent security configurations
    Check the OSGi configurations in the Apache Felix Web Console (at /system/console/configMgr) for any custom servlet filters or cross-site scripting protections, and review the X-Frame-Options and Content-Security-Policy header configurations
    Affected if No input validation or output encoding filters are configured and the version is vulnerable

You are affected if your installed Adobe Experience Manager version is 6.5.20 or earlier, or any version prior to the 2024.5 release, and URL parameters are reflected in responses without proper encoding.

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.21 / 2024.5 or later
Fixed in 6.5.212024.5
Interim mitigation

Update Adobe Experience Manager to version 6.5.21 or later to obtain the vendor patch. Additionally, implement output encoding and input validation on vulnerable endpoints as a defense-in-depth measure while planning the update.

Recommended fix High confidence

AEM 6.5.21 or later, or AEM 2024.5 or later

  1. Upgrade Adobe Experience Manager to version 6.5.21 or later
  2. Alternatively, upgrade to the 2024.5 release or later
  3. After upgrading, verify the XSS vulnerability is resolved by testing the previously vulnerable endpoint

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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