CVE-2024-43746
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 · uneditedAdobe 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 · moderate confidenceStored 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 is persisted in the system and executes when users view pages containing the compromised 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< 6.5.22.0< 2024.11.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed AEM versionAccess the AEM System Information console (typically at /system/console/systeminfo or /libs/granite/ui/content/shell/about.html) or check the 'About Adobe Experience Manager' page from the AEM welcome screenAffected if The installed version is earlier than 6.5.22.0 or earlier than 2024.11.0 (for 2024.x releases)
-
Determine if AEM Forms module is in useCheck whether the AEM Forms or Adaptive Forms functionality is installed and actively used in the environment. This can be verified by accessing the Forms console at /aem/forms or reviewing installed packages for 'forms' related bundlesAffected if AEM Forms or Adaptive Forms is installed and forms are being used - the vulnerability only affects form fields
-
Review form field configurations for suspicious contentInspect the form field definitions stored in the AEM content repository (typically under /content/forms/af or similar paths) and check for any unexpected script tags, event handlers, or encoded JavaScript in field labels, placeholders, or validation patternsAffected if Form field configurations contain script tags or JavaScript in fields that accept user input
-
Audit published content for injected scriptsReview the published pages containing form components. Examine the HTML source of rendered form pages to identify any malicious script payloads that may have been persisted and renderedAffected if Rendered HTML output from forms contains unsanitized script tags or event handlers that originated from user input
You are affected if your AEM version is below 6.5.22.0 (6.x line) or below 2024.11.0 (2024.x line) AND you have AEM Forms/Adaptive Forms enabled with user-accessible form fields.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.22.02024.11.0
Implement input validation and output encoding for form fields, or upgrade to a patched AEM version if available. Apply Content Security Policy headers as an additional defense layer.
AEM 6.5.22.0 (on-premise) or AEM as a Cloud Service 2024.11.0+
- Verify current Adobe Experience Manager version by accessing /system/console/bundles or checking the About Adobe Experience Manager page
- Review the Adobe Experience Manager 6.5.22 release notes for breaking changes and compatibility notes
- Ensure all custom code and third-party integrations are tested for 6.5.22.0 compatibility
- For AEM as a Cloud Service customers: verify the current release version in Cloud Manager and plan upgrade to 2024.11.0 or later
- For AEM 6.5 on-premise customers: download and install AEM 6.5.22.0 or later from the Adobe Software Distribution portal
- After upgrade, verify the XSS fix is applied by testing form field inputs with script injection payloads
- Clear the AEM cache and publish any updated content if necessary
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43746 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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