Health Check & Troubleshooting <= 1.2.3 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.2.4
- Affected Plugin
- Health Check & Troubleshooting
- Affected Version
<= 1.2.3- CVSS
- 8.0High
- 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 Health Check & Troubleshooting WordPress plugin, affecting versions <= 1.2.3. It carries a CVSS score of 8.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.2.4; sites on affected versions should update now. Disclosed January 2019, reported by Julien Legras.
Vulnerability Overview
The Health Check & Troubleshooting plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.2.3. This is due to missing or incorrect nonce validation. This makes it possible for authenticated attackers to call AJAX actions (vulnerable actions listed in resource) via 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. 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 Health Check & Troubleshooting <= 1.2.3 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 Health Check & Troubleshooting the fix is 1.2.4: builds <= 1.2.3 are affected, anything from 1.2.4 onward is not.
Remediation
Update to version 1.2.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Health Check & Troubleshooting: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Health Check & Troubleshooting 1.2.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Health Check & Troubleshooting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C