dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-41845

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 stored Cross-Site Scripting (XSS) vulnerability that could be abused by an attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.

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 contain a stored Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript into form fields, which persists and executes when users view pages containing those compromised fields.

MitigationUpdate Adobe Experience Manager to version 6.5.21 or later to apply the security patch, and implement proper input validation and output encoding on all form fields to prevent XSS.

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 Adobe Experience Manager installed version
    Navigate to the AEM Welcome page or access the system information console (usually at /system/console/status) to view the current AEM version number
    Affected if The installed version is 6.5.20 or earlier, OR the version is below 2024.5 (for newer release tracks)
  2. Verify if AEM Forms module is deployed
    Check the AEM package manager or list installed bundles to see if 'aem-forms' or 'forms' related packages are present and active
    Affected if AEM Forms is installed and active in the environment
  3. Identify custom form components in use
    Review the /apps directory for custom form components (look for components with 'form' in the path or name, especially custom field components) and check their JSP/HTL templates for output encoding
    Affected if Custom form components exist that do not use AEM's built-in encoding utilities like xssAPI or HTL context-aware attributes
  4. Inspect stored form data for unsanitized content
    Query the JCR (Java Content Repository) for form submission data in /content/forms or similar paths, and examine the raw stored values for any script tags or JavaScript event handlers
    Affected if Form submission data contains unencoded HTML or script tags that would execute when rendered

A user is affected if their AEM version is below 6.5.21 (or below 2024.5) AND they have AEM Forms or custom form components that store and display user input without proper output 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 apply the security patch, and implement proper input validation and output encoding on all form fields to prevent XSS.

Recommended fix High confidence

AEM 6.5.21+ or AEM 2024.6+ (for as-a-cloud-service)

  1. 1. Identify your current Adobe Experience Manager version by checking the AEM welcome page or system console
  2. 2. For AEM 6.5.x releases: Upgrade to AEM 6.5.21 or later
  3. 3. For AEM as a Cloud Service: Upgrade to 2024.6 release or later
  4. 4. After upgrade, verify the Forms component patches are applied through the AEM Package Manager
  5. 5. Test the form fields where user input is captured to confirm the XSS vulnerability is remediated
  6. 6. Clear AEM caches and rebuild any indexes if necessary after the upgrade
Caveat Review Adobe's release notes for the target version to check for any breaking changes or deprecations before upgrading

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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