Protected Posts Logout Button <= 1.4.4 - Cross-Site Request Forgery to Settings Update
Strategic Overview
- Status
- Patched in 1.4.5
- Affected Plugin
- Protected Posts Logout Button
- Affected Version
<= 1.4.4- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Protected Posts Logout Button WordPress plugin, affecting versions <= 1.4.4. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.4.5; sites on affected versions should update now. Disclosed February 2023.
Vulnerability Overview
The Protected Posts Logout Button plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.4.4. This is due to missing or incorrect nonce validation on the pplb_options_save function. This makes it possible for unauthenticated attackers to update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Protected Posts Logout Button <= 1.4.4 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Protected Posts Logout Button the fix is 1.4.5: builds <= 1.4.4 are affected, anything from 1.4.5 onward is not.
Remediation
Update to version 1.4.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Protected Posts Logout Button: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Protected Posts Logout Button 1.4.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Protected Posts Logout Button
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C