dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-43728

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. Attackers can inject malicious JavaScript into form fields, which persists in the system. When users browse to pages containing these compromised fields, the malicious scripts execute in their browsers, potentially stealing session cookies, credentials, or performing actions on behalf of the victim.

MitigationUpdate Adobe Experience Manager to version 6.5.22 or later. Additionally, implement robust input validation and output encoding on form fields as a defense-in-depth measure while the patch is being applied.

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 AEM Welcome page or check the crx/packmgr/service.jsp endpoint to identify the exact version number. Typically found at 'http://[host]:[port]/aem/start.html' or via the 'Version' column in Package Manager.
    Affected if The installed version is 6.5.21 or earlier, or falls below 2024.11.0 (for the 2024 release track).
  2. Verify form authoring is enabled
    Check if forms functionality is active by reviewing the AEM Forms UI at /aem/forms or by examining the presence of form-related content fragments or adaptive forms in the repository under /content/forms.
    Affected if Forms or adaptive forms are created and publicly accessible, as the XSS payload injects into form fields.
  3. Inspect form data storage for suspicious content
    Query the AEM repository (CRXDE Lite at /crx/de) or examine form submission data under /content/forms/af or similar paths for any unexpected script tags, javascript: URIs, or HTML event handlers.
    Affected if Any form field data contains persisted <script> tags, event handlers (onerror, onload, onclick), or javascript: pseudo-protocol entries.
  4. Review recent form submissions or content updates
    Check the AEM audit logs or content modification history via the 'Timeline' view in AEM Assets or via the Replication queue to identify recent form-related content authored by unexpected users.
    Affected if Form submissions originate from untrusted sources or contain encoded payloads that may represent attempted XSS injection.

You are affected if your AEM version is below 6.5.22.0 or 2024.11.0 AND you have forms enabled with user-submitted content that could contain malicious scripts.

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 Adobe Experience Manager to version 6.5.22 or later. Additionally, implement robust input validation and output encoding on form fields as a defense-in-depth measure while the patch is being applied.

Recommended fix High confidence

AEM 6.5.22.0 (for 6.5.x line) or AEM 2024.11.0 (for newer release line)

  1. 1. Identify the current AEM version in use (6.5.x line or 2024.x cloud/newer release line)
  2. 2. If running AEM 6.5.x version 6.5.21 or earlier, schedule upgrade to version 6.5.22.0 or later
  3. 3. If running AEM 2024.x version before 2024.11.0, schedule upgrade to version 2024.11.0 or later
  4. 4. After upgrade, verify that the XSS fix is applied by testing form field inputs with malicious script payloads
  5. 5. Review Adobe's release notes for any additional security fixes included in the target release
Caveat Minor releases may include compatibility changes; review Adobe's migration guide and test in non-production environment before deploying

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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