StaffList
stafflist · plugin
Known security vulnerabilities for StaffList. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
1 critical · 2 exploitable without logging in · 2 with no official fix seen · latest Nov 27, 2025
Before you install
Do not install
- 2 records show no fix in the latest wordpress.org release.
- 2 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 3.2.7 · last updated Nov 25, 2025 · 100+ installs
wordpress.org status checked on Nov 19, 2026
Vulnerabilities
- Critical 9.8
CVE-2022-1556admin→ 3.1.5
StaffList < 3.1.5 - Admin+ SQLi
- Medium 6.1
CVE-2024-13749unauthenticated · needs a click≤ 3.2.3
StaffList <= 3.2.3 - Cross-Site Request Forgery to Reflected Cross-Site Scripting
- Medium 5.3
CVE-2025-32255unauthenticatedno fix seen
WordPress StaffList plugin <= 3.2.7 - Sensitive Data Exposure vulnerability
- Medium 4.4
CVE-2025-12185admin≤ 3.2.6
StaffList <= 3.2.6 - Authenticated (Admin+) Stored Cross-Site Scripting
- Medium 4.3
CVE-2025-32232login requiredno fix seen
WordPress StaffList plugin <= 3.2.7 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (3.2.7) as affected.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.