CVE-2026-15727 json
WP Bulk Delete <= 1.4.2 - Authenticated (Administrator+) SQL Injection via 'delete_user_roles' Parameter
published 3mo ago modified 3mo ago also EUVD-2026-44900
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
The WP Bulk Delete plugin for WordPress is vulnerable to generic SQL Injection via the 'delete_user_roles' parameter in all versions up to, and including, 1.4.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. wp_unslash() is applied to the raw POST body before parse_str() decomposes it, stripping WordPress magic-quotes protection and leaving attacker-controlled values fully unescaped prior to reaching the SQL sink.
Is CVE-2026-15727 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected products
- xylus WP Bulk Delete
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/39d325d4-073c-47b6-8ea4-30637417f0d7?source=cve
- plugins.trac.wordpress.org /browser/wp-bulk-delete/tags/1.4.1/includes/class-delete-api.php#L1071
- plugins.trac.wordpress.org /browser/wp-bulk-delete/tags/1.4.2/includes/class-delete-api.php#L1113
- plugins.trac.wordpress.org /browser/wp-bulk-delete/tags/1.4.2/includes/class-delete-api.php#L1071
- plugins.trac.wordpress.org /browser/wp-bulk-delete/tags/1.4.2/includes/ajax-delete-handler.php#L36
- plugins.trac.wordpress.org /browser/wp-bulk-delete/tags/1.4.2/includes/ajax-delete-handler.php#L118
- plugins.trac.wordpress.org /browser/wp-bulk-delete/tags/1.4.1/includes/class-delete-api.php#L1113
- plugins.trac.wordpress.org /browser/wp-bulk-delete/tags/1.4.1/includes/ajax-delete-handler.php#L36
- plugins.trac.wordpress.org /browser/wp-bulk-delete/tags/1.4.1/includes/ajax-delete-handler.php#L118
- plugins.trac.wordpress.org /changeset/3608270/wp-bulk-delete/trunk/includes/class-delete-api.php
Sources
- CVE List CVE-2026-15727
- NVD CVE-2026-15727
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.