CVE-2026-4006 Draft List <= 2.6.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'display_name' Parameter

Medium 6.4 Published Updated

Authenticated attackers can inject arbitrary scripts via the display_name parameter in the Simple Draft List plugin, leading to stored XSS.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-4006?

CVE-2026-4006 is a medium-severity cross-site scripting vulnerability in dartiss Draft List, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

The Simple Draft List plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'display_name' post meta (Custom Field) in all versions up to and including 2.6.2. This is due to insufficient input sanitization and output escaping on the author display name when no author URL is present. The plugin accesses `$draft_data->display_name` which, because `display_name` is not a native WP_Post property, triggers WP_Post::__get() and resolves to `get_post_meta($post_id, 'display_name', true)`. When the `user_url` meta field is empty, the `$author` value is assigned to `$author_link` on line 383 without any escaping (unlike line 378 which uses `esc_html()` for the `{{author}}` tag, and line 381 which uses `esc_html()` when a URL is present). This unescaped value is then inserted into the shortcode output via `str_replace()`. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses a page containing the `[drafts]` shortcode with the `{{author+link}}` template tag.

Weakness: CWE-79

Which versions are affected by CVE-2026-4006?

How do I fix CVE-2026-4006?

No fix has been published for CVE-2026-4006 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-4006 being exploited?

There is no known exploitation of CVE-2026-4006 in the wild and no public exploit code.

Sources

Also known as GHSA-5m2m-h2j8-8xvj.

Is CVE-2026-4006 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free