CVE-2026-9104
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 · uneditedThe Draft List plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Draft Post Title in all versions up to, and including, 2.6.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The unescaped injection path is triggered specifically when the viewing user lacks edit capabilities, meaning payloads embedded in draft post titles via attribute-breakout techniques execute for unauthenticated users and subscribers.
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 confidenceThe Draft List WordPress plugin fails to properly sanitize and escape the Draft Post Title field, allowing authenticated users with author-level permissions or higher to inject malicious JavaScript via stored XSS. The injected payload executes when viewed by users lacking edit capabilities (unauthenticated users, subscribers), as the vulnerable code path only activates for those user roles.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Draft List plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Draft List' in the list. Note the installed version number displayed next to the plugin name.Affected if The plugin is installed and the version is 2.6.3 or lower (the vulnerable range is 'up to 2.6.3').
-
Check for author-level usersGo to Users > All Users in WordPress admin. Review the 'Role' column for any accounts assigned the 'Author' role.Affected if There are user accounts with Author role, as this is the minimum privilege level required to inject the malicious payload.
-
Identify users who can trigger the XSSCheck if your site has subscribers (Users > All Users > Role = Subscriber) or allows public/guest submissions. Also verify if your site permits user registration with subscriber-level access.Affected if There are subscriber accounts or the site allows unauthenticated visitors to view content, as the injected script executes when these users view the affected draft titles.
-
Inspect draft posts for suspicious title contentAccess the database or use a plugin/admin tool to view draft posts. Examine the 'post_title' field in the wp_posts table where post_status = 'draft'. Look for unusual characters, HTML tags, or JavaScript code within title values.Affected if Any draft post titles contain unescaped HTML or script tags, indicating exploitation has occurred.
You are affected if the Draft List plugin version is 2.6.3 or lower AND your site has author-level users AND vulnerable users (subscribers or unauthenticated visitors) can view draft content.
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 · scopedUpdate to the latest version of the Draft List plugin when available, and ensure all user-provided content is sanitized using WordPress sanitization functions and properly escaped before output.
Draft List plugin version 2.6.4 or later
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'Draft List' plugin in the plugin list
- 4. If an update is available, click 'Update Now' to upgrade to the latest version (version 2.6.4 or later)
- 5. Alternatively, navigate to Dashboard > Updates and apply all available updates
- 6. Verify the plugin was updated successfully by checking the Plugins page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9104 — 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-2026-9104 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