The WP Roster WordPress plugin before 2.35 does not perform any capability or nonce checks on one of its AJAX actions
Source GCVE Database
Not known to be exploited : upgrade to 2.35 soon.
Data as of 28 Oct 2026, 07:14 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 2.35
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade WP Roster to 2.35.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Roster | Affected
| Fixed in
|
AI-suggested
Upgrade the WP Roster plugin to version 2.35 or later where this vulnerability is fixed. If upgrading immediately is not possible, restrict access to the affected AJAX action by implementing custom capability and nonce checks as a temporary measure.
Description
The WP Roster WordPress plugin versions prior to 2.35 contain a vulnerability where one of its AJAX actions lacks capability and nonce checks. This flaw allows unauthenticated attackers to delete WordPress user accounts of roster members.