dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-43751

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.21 and earlier. Attackers can inject malicious JavaScript into vulnerable form fields, which executes in victim browsers when they view the affected page.

MitigationApply the vendor patch (upgrade to AEM 6.5.22 or later) and sanitize existing form data to remove any injected malicious scripts.

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 version
    Access the AEM Welcome page or run 'java -jar cq-quickstart*.jar -version' from the installation directory. Alternatively, check the version in the 'crx-quickstart/package.xml' file or via the system console at /system/console/bundles (look for Adobe Experience Manager bundle version).
    Affected if The installed version is 6.5.21 or earlier, or any version below 2024.11.0 (for example, 6.5.0 through 6.5.21, or 2024.x versions below 2024.11.0).
  2. Confirm AEM Forms module is in use
    Check if the AEM Forms add-on is installed by navigating to /libs/fd/fm/view/ or checking the 'AEM Forms' tile on the AEM Welcome page. Look for form components under /libs/foundation/components/form/ in CRX/DE Lite (accessible at /crx/de/index.jsp).
    Affected if AEM Forms module is installed and forms are being used on the publish or author instances.
  3. Inspect form configurations for missing output encoding
    Navigate to the form component definitions in CRX/DE Lite under /apps or /libs. Check the JSP or HTL files (for example, in /libs/foundation/components/form/text, /libs/fd/fm/components) for whether they use context-aware encoding (such as 'out.escapeHtml()' in JSP or '${resource.properties @ context='html'}' in HTL) when rendering form field values.
    Affected if Form field values are rendered without proper context-aware output encoding, allowing unsanitized user input to be stored and displayed.
  4. Scan stored form data for malicious scripts
    Use CRX/DE Lite (at /crx/query.jsp) or the Query Builder API to search form submission nodes (typically under /content/forms/af or custom form content paths) for patterns like '<script', 'javascript:', 'onerror=', 'onload=', or other XSS vectors in stored field values.
    Affected if Form submission data contains unsanitized HTML or JavaScript payloads that were successfully stored in the repository.

You are affected if your AEM version is below 6.5.22.0 or below 2024.11.0, AND you are using AEM Forms with form fields that accept 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.22.0 / 2024.11.0 or later
Fixed in 6.5.22.02024.11.0
Interim mitigation

Apply the vendor patch (upgrade to AEM 6.5.22 or later) and sanitize existing form data to remove any injected malicious scripts.

Recommended fix High confidence

6.5.22.0 (for 6.5.x LTS branch)

  1. Identify the current Adobe Experience Manager version by checking the AEM About page or version.properties file
  2. Determine your release track: 6.5.x (LTS) or 2024.x (Cloud Service/Continuous Delivery)
  3. Review Adobe Experience Manager release notes for the target fixed version
  4. Create a full backup of the AEM instance including repository, configurations, and any custom code
  5. Schedule a maintenance window for the upgrade process
  6. Follow Adobe's official upgrade documentation for your specific version path
  7. After completing the upgrade, verify the XSS vulnerability is resolved by testing form fields with malicious script payloads
  8. Clear AEM caches and rebuild search indexes if necessary
Caveat Review release notes for compatibility changes with custom components, integrations, or third-party plugins

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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