WP Symposium Pro < 16.01 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 16.01
- Affected Plugin
- WP Symposium Pro
- Affected Version
< 16.01- 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 WP Symposium Pro WordPress plugin, affecting versions < 16.01. 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 16.01; sites on affected versions should update now. Disclosed January 2016, reported by Rahul Pratap Singh.
Vulnerability Overview
The WP Symposium Pro plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions before 16.01. This is due to missing or incorrect nonce validation on the edit profile page. This makes it possible for unauthenticated attackers to change a user's password leading to full account takeover 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)
Reaching this weakness in WP Symposium Pro < 16.01 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 WP Symposium Pro the fix is 16.01: builds < 16.01 are affected, anything from 16.01 onward is not.
Remediation
Update to version 16.01, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Symposium Pro: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Symposium Pro 16.01 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP Symposium Pro
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C