WordPress Restrict User Access – Membership plugin with Force plugin <= 2.8.3 - Broken Access Control vulnerability

published 2026-11-11 23h ago modified 2026-11-11 22h ago also EUVD-2026-123370

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

Missing Authorization vulnerability in DEV Institute Restrict User Access – Membership Plugin with Force restrict-user-access allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Restrict User Access – Membership Plugin with Force: from n/a through 2.8.3.

Patch / fix

fixed in 1

DEV Institute Restrict User Access – Membership Plugin with Force 2.8.4

Is CVE-2026-115600 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 Fencer

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

DEV Institute Restrict User Access – Membership Plugin with Force

Classification

Weakness

CWE-862 Missing Authorization

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/restrict-user-access/vulnerability/wordpress-restrict-user-access-membership-plugin
vdb-entry

Sources

CVE List CVE-2026-115600
NVD CVE-2026-115600

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.