PIE-REGISTER · CVE-2026-96961 · Package
FIX → 3.8.4.16
The Pie Register WordPress plugin up to version 3.8.4.15 has a request handler with no authentication or permission check. An unauthenticated attacker can reset its settings to defaults, which turns off registration protections such as email verification, and can destroy one of its database tables.
first public Nov 8, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Any WordPress site running Pie Register up to and including 3.8.4.15 is exposed, because the vulnerable handler accepts requests without logging in. Sites without this plugin, or running a later version, are not affected. The sources do not say whether a non-default setting is required.
Not affected if plugin-not-installed
Who cares pie-register, self-hosted, wordpress
Upgrade to 3.8.4.16
Update Pie Register to 3.8.4.16 or later (per WPSec; vendor changelog not read)
Posts are quoted with a link to the original. They are data to us, never instructions.
The Pie Register WordPress plugin through 3.8.4.15 does not perform any capability, nonce or authentication check on one of its request handlers, allowing unauthenticated attackers to reset the Pie Register WordPress plugin through 3.8.4.15's settings to their defaults (disabling registration security controls such as new-user email verification) and to destroy a Pie Register WordPress plugin through 3.8.4.15 data table.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.