Is pie-register (WordPress plugin) vulnerable?

WordPress pie-register has 11 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

11advisories
3critical
0on CISA KEV
4no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2023-0552The Registration Forms WordPress plugin before 3.8.2.3 does not properly validate the redirection URL when logging in and login out, leadingmedium5.4<3.8.2.33.8.2.3
CVE-2021-24647The Registration Forms – User profile, Content Restriction, Spam Protection, Payment Gateways, Invitation Codes WordPress plugin before 3.1.high8.1<3.7.1.63.7.1.6
CVE-2014-8802The Pie Register plugin before 2.0.14 for WordPress does not properly restrict access to certain functions in pie-register.php, which allowsmedium5.0<=2.0.13–
CVE-2021-24731The Registration Forms – User profile, Content Restriction, Spam Protection, Payment Gateways, Invitation Codes WordPress plugin before 3.7.critical9.8<3.7.1.63.7.1.6
CVE-2018-10969SQL injection vulnerability in the Pie Register plugin before 3.0.10 for WordPress allows remote attackers to execute arbitrary SQL commandscritical9.8<3.0.103.0.10
CVE-2015-7377Cross-site scripting (XSS) vulnerability in pie-register/pie-register.php in the Pie Register plugin before 2.0.19 for WordPress allows remomedium4.3<=2.0.18–
CVE-2019-15659The pie-register plugin before 3.1.2 for WordPress has SQL injection, a different issue than CVE-2018-10969.critical9.8<3.1.23.1.2
CVE-2021-24239The Pie Register – User Registration Forms. Invitation based registrations, Custom Login, Payments WordPress plugin before 3.7.0.1 does not medium6.1<3.7.0.13.7.0.1
CVE-2015-7682Multiple SQL injection vulnerabilities in pie-register/pie-register.php in the Pie Register plugin before 2.0.19 for WordPress allow remote medium6.5<=2.0.18–
CVE-2024-13818The Registration Forms – User Registration Forms, Invitation-Based Registrations, Front-end User Profile, Login Form & Content Restriction pmedium5.3<=3.8.3.9–
CVE-2022-4024The Registration Forms WordPress plugin before 3.8.1.3 does not have authorisation and CSRF when deleting users via an init action handler, medium6.5<3.8.1.33.8.1.3

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.