Strategic Overview
- Status
- Patched in 7.1.10
- Affected Plugin
- WP Spell Check
- Affected Version
<= 7.1.9- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2019-6027
At a glance
CVE-2019-6027 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Spell Check WordPress plugin, affecting versions <= 7.1.9. 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 7.1.10; sites on affected versions should update now. Disclosed November 2019, reported by Takuya Yamaguchi.
Vulnerability Overview
Cross-site request forgery (CSRF) vulnerability in WP Spell Check 7.1.9 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.
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 Spell Check <= 7.1.9 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 Spell Check the fix is 7.1.10: builds <= 7.1.9 are affected, anything from 7.1.10 onward is not.
Remediation
Update to version 7.1.10, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Spell Check: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Spell Check 7.1.10 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Spell Check
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C