CVE-2026-115257: WP Roster · Improper Access Control
Affects WP RosterSource CVE Database V5
Not known to be exploited : upgrade to 2.36 soon.
Data as of 4 Nov 2026, 06:17 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 WP Roster to version 2.36 or later, where proper capability and nonce checks have been implemented to prevent unauthorized roster modifications.
Description
A vulnerability in the WP Roster WordPress plugin before version 2.36 allows unauthenticated attackers to overwrite, wipe, or restore roster content due to missing capability and nonce checks.