CVE-2024-26122
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 browsers when they 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.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.
-
Check Adobe Experience Manager versionAccess the AEM Web Console at /system/console/configMgr or check the version from the AEM Welcome page at /libs/cq/core/content/welcome.html. The version number is displayed in the AEM logo or under 'Version' in the system information.Affected if The installed version is 6.5.19.x or earlier, or any version below 6.5.20.0, or any version below 2024.3.0.
-
Verify AEM 2024 release train versionNavigate to /system/console/config and look for the 'Adobe Experience Manager' entry or check the crx/packmgr console for the core com.adobe.aemforms.version entry. The 2024.x versions are identified by the year-month format in the package version.Affected if The 2024 release train version is earlier than 2024.3.0.
-
Identify custom form components in useReview the /apps and /libs directories for custom form field components. Search for files containing form field components such as input, textarea, or select xtypes. Check content pages that render forms for custom field implementations.Affected if Custom form field components exist in /apps that override the core form components without proper input validation.
-
Check form field configurations for missing input validationReview the XML or JSON configuration files for form components in your content structure. Inspect thegranite:dataType and sling:resourceType properties on form field nodes under /content to see if custom components are being used.Affected if Form field components use custom renderers without validated input patterns or output encoding configured.
-
Audit stored form data for suspicious contentQuery the JCR repository using CRXDE Lite or the Query tool (http://localhost:4502/crx/explorer/query.jsp) to search for script tags in form field values. Use a SQL2 query like SELECT * FROM [nt:unstructured] WHERE [sling:resourceType] LIKE '%form%' and contains(*, '<script').Affected if Any form field nodes contain persisted HTML or script tags that could indicate exploitation.
You are affected if your AEM version is below 6.5.20.0 (for the 6.5.x train) or below 2024.3.0 (for the 2024 train), AND your implementation uses custom form field components that accept and persist user input without output encoding.
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
Update Adobe Experience Manager to version 6.5.20 or later to obtain the security patch. Additionally, implement input validation and output encoding on form fields as defense-in-depth until the patch is applied.
Adobe Experience Manager 6.5.20.0 or 2024.3.0
- Review the Adobe Experience Manager upgrade documentation for your current version
- Plan and schedule the upgrade during a maintenance window
- Back up your current AEM instance including the repository, database, and configurations
- Test the upgrade in a staging environment before production deployment
- Upgrade Adobe Experience Manager to version 6.5.20.0 or later (for 6.5.x releases)
- OR upgrade to version 2024.3.0 or later (for the 2024 release cycle)
- Verify the upgrade was successful and all services are running
- Test that the XSS vulnerability is no longer exploitable in the form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26122 — 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-26122 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