Spam Protection | Maspik
contact-forms-anti-spam · plugin
Known security vulnerabilities for Spam Protection | Maspik. Find out in seconds which version runs on your site with WP Lens.
8 known vulnerabilities
5 exploitable without logging in · latest Aug 13, 2026
Listed on wordpress.org · latest 3.1.3 · last updated Sep 29, 2026 · 30K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2023-24008unauthenticated · needs a click≤ 0.7.8
WordPress Maspik – Spam blacklist Plugin <= 0.7.8 is vulnerable to Cross Site Request Forgery (CSRF)
- High 7.1
CVE-2026-28003unauthenticated · needs a click≤ 2.9.1
WordPress Maspik – Spam blacklist plugin <= 2.9.1 - Cross Site Scripting (XSS) vulnerability
- Medium 6.1
CVE-2023-48272unauthenticated · needs a click≤ 0.9.2
WordPress Maspik – Spam blacklist Plugin <= 0.9.2 is vulnerable to Cross Site Scripting (XSS)
- Medium 5.4
CVE-2024-53806login required≤ 2.2.7
WordPress Maspik plugin <= 2.2.7 - CSRF to Settings Change vulnerability
- Medium 5.3
CVE-2023-48271unauthenticated≤ 0.10.3
WordPress Maspik – Spam Blacklist plugin <= 0.10.3 - IP Filtering Bypass vulnerability
- Medium 4.8
CVE-2024-25101high privilege≤ 0.10.6
WordPress Maspik – Spam blacklist Plugin <= 0.10.6 is vulnerable to Cross Site Scripting (XSS)
- Medium 4.3
CVE-2025-9888unauthenticated · needs a click≤ 2.5.6
Maspik <= 2.5.6 - Cross-Site Request Forgery
- Medium 4.3
CVE-2025-9979subscriber+≤ 2.5.6
Maspik <= 2.5.6 - Authenticated (Subscriber+) Missing Authorization to Spam Log Export
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).