CVE-2024-26028
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 form input that persists on the server, which then executes in victim users' browsers when they view the affected page.
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.
-
Verify AEM versionCheck the installed Adobe Experience Manager version through the AEM Web Console (Navigate to Help > About Adobe Experience Manager) or by viewing the version.properties file in the crx-quickstart folder. Compare the version number to the affected ranges: below 6.5.20.0 or below 2024.3.0.Affected if The installed version is below 6.5.20.0 or below 2024.3.0
-
Identify custom form componentsReview the /apps directory in CRXDE Lite for custom form field components (look in /apps for nodes of type cq:Component that extend form field foundations). Check the JSP or HTL templates for these components to see if they use output encoding (such as the xss API or encoding.escapeHtml() in HTL) when rendering form input values.Affected if Custom form components exist that do not perform output encoding on user-supplied values when rendering them back to the page
-
Audit stored form data for XSS payloadsQuery the JCR repository (using CRXDE Lite or a JCR SQL2 query) for form container or form field nodes under /content that contain script tags, javascript: URIs, or HTML event attributes (onerror, onload, onClick, etc.) in text fields. Example: search node text for patterns like <script, javascript:, onerror=, onload=.Affected if Form data in the repository contains persisted malicious script tags or event handlers that would execute when the page is viewed
-
Check if vulnerable form pages are publicly accessibleReview the content structure under /content to identify form pages that are exposed via publish instances or dispatcher. Verify whether anonymous users can access and submit forms on these pages.Affected if Form pages with unencoded output are accessible to unauthenticated or low-privilege users who could inject payloads
You are affected if your AEM version is below 6.5.20.0 or below 2024.3.0 AND you have custom form components that render user input without proper output encoding, allowing stored XSS payloads to persist and execute in other users' browsers.
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
Upgrade to AEM 6.5.20 or later. Until then, implement input validation and output encoding on all form fields, and consider Content Security Policy headers to mitigate XSS execution.
AEM 6.5.20.0 (for 6.5.x line) or AEM 2024.3.0 (for cloud/2024.x line)
- 1. Review the Adobe security bulletin at helpx.adobe.com for CVE-2024-26028 to understand full context and any additional requirements
- 2. Identify your current AEM version (6.5.x line or cloud/2024.x line)
- 3. For AEM 6.5.x installations: Plan upgrade to version 6.5.20.0
- 4. For AEM as a Cloud Service or 2024.x releases: Plan upgrade to version 2024.3.0
- 5. Create a complete backup of the current AEM instance including content and configuration
- 6. Test the upgrade in a staging or development environment before production deployment
- 7. Verify all custom code and integrations function correctly post-upgrade
- 8. Deploy the upgraded version to production environment
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-26028 — 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-26028 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