Is sensei-lms (WordPress plugin) vulnerable?

WordPress sensei-lms has 5 known advisories in the phpwarden feed. Feed 2026.10.28.3, updated 2026-10-28.

5advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2022-2034The Sensei LMS WordPress plugin before 4.5.0 does not have proper permissions set in one of its REST endpoint, allowing unauthenticated usermedium5.3<4.5.04.5.0
CVE-2024-7786The Sensei LMS WordPress plugin before 4.24.2 does not properly protect some its REST API routes, allowing unauthenticated attackers to leamedium5.3<4.24.24.24.2
CVE-2022-2080The Sensei LMS WordPress plugin before 4.5.2 does not ensure that the sender of a private message is either the teacher or the original sendmedium4.3<4.5.24.5.2
CVE-2025-0466The Sensei LMS WordPress plugin before 4.24.4 does not properly protect some its REST API routes, allowing unauthenticated attackers to leakmedium5.3<4.24.44.24.4
CVE-2024-8009The Sensei LMS WordPress plugin before 4.20.0 disclose all users of the blog including their email address to teachers on the students pagemedium4.3<4.20.04.20.0

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.