CVE-2024-26043
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.19 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 confidenceAdobe Experience Manager versions 6.5.19 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. Attackers can inject malicious JavaScript into vulnerable form inputs, which persists in the system and executes in victim users' browsers when they view pages containing the affected 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.20.0< 2024.3.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.
-
Determine AEM versionLog in to AEM as administrator and navigate to Tools > Operations > Web Console, or check the version from the felix console at /system/console/bundles. Alternatively, locate the file 'crx-quickstart/conf/org.apache.felix.framework.properties' or check the 'product.version' in the AEM SDK.Affected if The installed version is below 6.5.20.0 or below 2024.3.0 (e.g., 6.5.19.x, 6.5.18.x, 2024.2.x, etc.)
-
Identify if AEM Forms is deployedNavigate to /libs/fd/fm/view/forms in the CRX/DE Lite (accessible at /crx/de/index.jsp) or check for the presence of the Forms Manager bundle at /system/console/bundles. Also check if form-related content packages are installed.Affected if AEM Forms module or Adaptive Forms feature is installed and active in the environment
-
Audit form field components in useIn CRX/DE Lite, navigate to /content (or relevant content paths) and search for form container components (nt:unstructured nodes with 'sling:resourceType' containing 'fd/af/fields' or similar form field resource types). Use Query Builder to search for nodes of type 'nt:unstructured' under /content that contain form field components.Affected if Form field components derived from AEM Forms (adaptive forms or core components with form functionality) are present in the content repository
-
Inspect form field input configurationsCheck the form field component nodes in CRX/DE Lite for 'name' and 'value' properties. Examine whether input validation rules are defined at /libs/fd/af/components/validation or custom validation is applied to form fields.Affected if Form fields exist without custom input validation rules or without XSS protection configuration applied at the field or form container level
-
Check for existing XSS protectionReview the XSS protection configuration at /libs/xss/config.xml or custom XSS filter configurations in /apps. Examine form field rendering templates under /libs/fd/af/renderers or core form components to verify if output encoding is applied using AEM's XSSAPI.Affected if No XSS filter rules are configured or the XSS protection is disabled (xss.enabled=false in the configuration)
If the AEM version is below 6.5.20.0 or below 2024.3.0 AND AEM Forms with form fields is deployed in the environment, the system is likely affected by this stored XSS vulnerability.
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.20.02024.3.0
Apply the AEM security patch for CVE-2024-26043. Additionally, implement output encoding and input validation on form fields using AEM's XSS protection features or custom sanitization to prevent script injection.
AEM 6.5.20.0 or AEM 2024.3.0+
- Backup your AEM instance including the repository, database, and configurations
- Review Adobe's official upgrade documentation for your current version
- Download Adobe Experience Manager 6.5.20.0 (or 2024.3.0+ for the newer release) from the Adobe distribution center
- Install the upgrade following Adobe's standard upgrade procedures
- Verify the upgrade completed successfully by checking the AEM version in the About Adobe Experience Manager page
- Test that the application functionality works as expected
- Validate that the stored XSS vulnerability is no longer present in form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26043 — 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-26043 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