CVE-2024-43748
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 · high 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. When victims browse to pages containing these compromised fields, the malicious scripts execute in their browsers, potentially stealing session cookies or performing actions on behalf of the user.
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 the installed AEM versionLog into the AEM Web Console or access the Help menu > About Adobe Experience Manager to view the installed version numberAffected if The version shown is 6.5.21 or earlier, or any version below 2024.11.0
-
Determine if AEM Forms module is enabledNavigate to the AEM Felix Console at /system/console/bundles or check the main AEM navigation for the Forms section. Look for the 'Adobe Experience Manager Forms' bundle or Forms-related packages in the installed stateAffected if The Forms bundle is active and forms can be created or accessed in the environment
-
Check if Forms are exposed to external or untrusted usersReview the AEM instance's web tier configuration, dispatcher settings, or publish tier deployments to identify whether any form-based pages are accessible to unauthenticated or external usersAffected if Form fields can be populated by users who are not trusted authors or administrators
-
Inspect form field configurations for sanitization settingsAccess the form definition through AEM Forms UI at /aem/forms or examine the form model XML/JSON configuration files in the repository under /conf or /content to review how input fields are configuredAffected if Form field components do not enforce input sanitization or content security policies, allowing script tag injection into field values
The environment is affected if the installed AEM version is below 6.5.22.0 or below 2024.11.0 AND forms with user-accessible input fields are present and exposed in the environment.
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
Update Adobe Experience Manager to version 6.5.22 or later to patch the vulnerability. After updating, verify that form fields properly sanitize user input and consider reviewing existing content for any injected malicious scripts.
AEM 6.5.22.0 or later; AEM as a Cloud Service 2024.11.0 or later
- Identify the current Adobe Experience Manager version in use (AEM 6.5.x or AEM as a Cloud Service)
- For AEM 6.5.x installations: Upgrade to version 6.5.22.0 or later
- For AEM as a Cloud Service: Upgrade to version 2024.11.0 or later
- After upgrading, verify the XSS vulnerability is remediated by testing form fields for proper input sanitization
- Confirm that content authors can no longer inject malicious scripts into vulnerable form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43748 — 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-43748 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