dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-43747

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

A stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.21 and earlier allows attackers to inject malicious JavaScript into form fields. The malicious payload persists in the system and executes when users view pages containing the affected form fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.22 or later to obtain the official security patch. As defense-in-depth, implement strict input validation and output encoding on form fields.

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 installed AEM version
    Access the AEM Web Console or check the version.properties file in the crx-quickstart folder. Navigate to /system/console/osgi-instal or run 'java -jar cq-quickstart-*.jar -version' if available.
    Affected if The installed version is below 6.5.22.0 or below 2024.11.0 (for the newer release track)
  2. Confirm AEM Forms module is in use
    Check if the AEM Forms add-on package is installed by reviewing installed packages in the Package Manager (/crx/packmgr) or checking for forms-related bundles in the OSGi console (/system/console/bundles).
    Affected if AEM Forms or Adaptive Forms components are installed and active in the environment
  3. Review form field configurations for missing input validation
    Navigate to the form authoring UI or inspect form models in CRX/DE (crx/de/index.jsp) under /content/forms/af or /libs/fd/af. Check if form field components have input validation rules enabled.
    Affected if Form fields lack input validation constraints or allow unrestricted text input
  4. Inspect stored form submissions for malicious payloads
    Query the AEM repository (via CRXDE or the Query tool) for form submission data in /content/forms/fg or check the submitted data in the Forms Manager. Look for script tags, javascript: handlers, or event attributes in field values.
    Affected if Form submission data contains unsanitized HTML, script tags, or JavaScript event handlers
  5. Check form output rendering for encoding
    Examine the JSP or HTL templates responsible for rendering form field values in the publish instance. Verify if output encoding (such as escaping HTML characters) is applied before displaying form data.
    Affected if Form values are rendered without proper HTML encoding or output escaping

A user is affected if they run AEM versions below 6.5.22.0 or below 2024.11.0 with AEM Forms enabled and form fields that accept user input without validation or 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

Upgrade Adobe Experience Manager to version 6.5.22 or later to obtain the official security patch. As defense-in-depth, implement strict input validation and output encoding on form fields.

Recommended fix High confidence

AEM 6.5.x: upgrade to 6.5.22.0 or later; AEM 2024.x: upgrade to 2024.11.0 or later

  1. Identify the current Adobe Experience Manager version in use
  2. For AEM 6.5.x installations: upgrade to version 6.5.22.0 or later
  3. For AEM as a Cloud Service / 2024 releases: upgrade to 2024.11.0 or later
  4. After upgrading, verify the XSS vulnerability is resolved by testing form fields that previously accepted malicious scripts
  5. Review Adobe's upgrade documentation for your specific deployment model before proceeding
Caveat Review Adobe's release notes for the target version for any compatibility or deprecation notices specific to your implementation

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
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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