The WP Roster WordPress plugin before 2.36 does not perform any capability or nonce checks before writing its stored
Source GCVE Database
Not known to be exploited : upgrade to 2.36 soon.
Data as of 4 Nov 2026, 07:29 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.36
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 3 Nov 2026.
What to do
Upgrade WP Roster to 2.36.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Roster | Affected
| Fixed in
|
AI-suggested
Upgrade the WP Roster plugin to version 2.36 or later where this issue is fixed. No other mitigation guidance is provided in the source data.
Description
The WP Roster WordPress plugin versions prior to 2.36 lack capability and nonce checks when writing stored roster data. This flaw allows unauthenticated attackers to overwrite, wipe, or restore any roster content.