dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-43752

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 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.21 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. User-supplied input in forms is not properly sanitized before storage, allowing malicious JavaScript to persist. When other users view pages containing these compromised form fields, the injected script executes in their browsers.

MitigationUpdate to Adobe Experience Manager version 6.5.22 or later. Until patch is available, implement output encoding on all form field renders and consider Content Security Policy headers to mitigate XSS execution.

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. Check installed AEM version
    Navigate to the AEM welcome page or access the System Information console (typically at /system/console/status/productinfo or /libs/granite/ui/content/shell/about.html). The version number is displayed in the product information section.
    Affected if The displayed version is below 6.5.22.0 (for 6.5.x releases) or below 2024.11.0 (for the 2024 release cycle).
  2. Verify AEM 6.5.x version number
    If using the 6.5.x release line, check the exact version in the AEM Web Console or by viewing the crx-quickstart folder properties. The version format is 6.5.x.
    Affected if The version shows 6.5.21 or earlier.
  3. Verify AEM 2024 release version
    If using the newer release naming (year.month), confirm the full version number in the About Adobe Experience Manager page or the productinfo endpoint.
    Affected if The version shows 2024.10 or earlier (anything below 2024.11).
  4. Confirm Form functionality is in use
    Review the AEM instance for deployed Forms components, Adaptive Forms, or custom form implementations. Check for form-related content fragments or form containers in the content tree under /content.
    Affected if Forms that accept user-supplied input are authored, stored, and rendered on the AEM instance.
  5. Inspect form field storage and output
    Examine a published page or preview that renders form fields. Submit test input containing script-safe characters (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>) in a form field, then view the stored content or the rendered page to see if the script executes.
    Affected if The submitted script tags render as raw HTML/JavaScript instead of being escaped or neutralized, indicating the XSS vulnerability is present.

You are affected if your AEM version is 6.5.21 or earlier (6.5.x branch) or 2024.10 or earlier (2024 branch) AND your instance has form fields that accept and display user input without 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.22.0 / 2024.11.0 or later
Fixed in 6.5.22.02024.11.0
Interim mitigation

Update to Adobe Experience Manager version 6.5.22 or later. Until patch is available, implement output encoding on all form field renders and consider Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

AEM 6.5.22.0 or AEM 2024.11.0 (whichever release train applies)

  1. Plan and schedule an upgrade to Adobe Experience Manager version 6.5.22.0 or later (for 6.5.x releases), or version 2024.11.0 or later (for cloud releases)
  2. Review the official Adobe Experience Manager upgrade documentation for your current version to understand the upgrade path
  3. Perform a complete backup of the current AEM instance and verify restore procedures
  4. Test the upgrade in a non-production environment to verify compatibility with custom code and configurations
  5. Deploy the upgraded version to production after successful testing
Caveat Review AEM release notes for potential breaking changes between your current version and the target version before upgrading

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
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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