WPBook <= 2.7 - Unauthenticated Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.7.1
- Affected Plugin
- WPBook
- Affected Version
<= 2.7- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPBook WordPress plugin, affecting versions <= 2.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.7.1; sites on affected versions should update now. Disclosed July 2015, reported by Planet zuda.
Vulnerability Overview
The WPBook plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.7. This is due to missing nonce validation on the wpbook_subpanel() function. This makes it possible for unauthenticated attackers to modify a vulnerable sites Facebook connection 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
WPBook <= 2.7 carries this weakness at wpbook_subpanel(), and reaching it takes no account at all. 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 WPBook the fix is 2.7.1: builds <= 2.7 are affected, anything from 2.7.1 onward is not.
Remediation
Update to version 2.7.1, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPBook 2.7.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C