CVE-2024-26081
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.20 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 confidenceAdobe Experience Manager versions 6.5.20 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where malicious scripts can be injected into form fields. When victims browse to pages containing these compromised fields, the injected JavaScript executes in their browsers, potentially enabling session hijacking, data theft, or further propagation.
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.21< 2024.5CVSS 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 your Adobe Experience Manager versionAccess the AEM Welcome page or check the version.properties file in the crx-quickstart directory. Alternatively, query the /system/console/bundles.json endpoint or check the Product Info in the AEM Web Console.Affected if The installed version is 6.5.20 or earlier, or falls below 2024.5
-
Verify if Forms module is in useCheck if AEM Forms is installed and active by reviewing installed packages via the Package Manager or checking for form-related content pages under /content/forms in the repository.Affected if Forms are present and accessible to external users or authors
-
Inspect form field configurations for input validationReview the form component XML definitions (for example, under /libs/foundation/components/form or custom form schemas) and check the granite:dataTypes or allowed pattern configurations to see if input validation is enforced.Affected if Form fields lack input validation rules or allow unrestricted text input
-
Search for suspicious script content in form dataQuery the JCR repository using CRXDE Lite or a repository search for common XSS patterns in form field values, such as <script, javascript:, onload=, onerror=, or encoded variants within /content/forms nodes.Affected if Any stored scripts are found in form field data entries
You are affected if your AEM version is below 6.5.21 (or below 2024.5) and your forms accept user input that could contain injected scripts without validation.
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.212024.5
Upgrade Adobe Experience Manager to a version newer than 6.5.20 or apply the relevant security patch. Additionally, implement input validation and output encoding on all form fields to prevent script injection.
AEM 6.5.21+ or AEM 2024.5+
- Upgrade Adobe Experience Manager to version 6.5.21 or later if on the 6.5.x release line
- Alternatively, upgrade to version 2024.5 or later if on the newer release track
- After upgrading, verify that the XSS vulnerability is remediated by testing form fields that previously allowed script injection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26081 — 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-26081 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