Plugins · health-check · data as of 2026-11-04
Is Health Check & Troubleshooting safe? Known vulnerabilities and latest version
- Latest version
- 1.7.1
- Last updated
- 2024-07-25
- Active installs
- 200,000+
- Known issues on record
- 2
- Unpatched in latest
- 1
- Tested up to WP
- 6.6.11 · PHP 5.6+
Health Check identifies common problems, and helps you troubleshoot plugin and theme conflicts. — by WordPress.org
What to do
- There is no fixed version yet. If you can live without Health Check & Troubleshooting for now, deactivate it and delete it until the developer ships a fix.
- If you must keep it, limit who can log in (remove unused accounts, especially low-level ones) and put a web application firewall in front of the site.
- Watch for an update: get an email when this page changes.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI: wp plugin get health-check --field=version shows what you run; wp plugin update health-check updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 4.9 affects latest 1.7.1 CVE-2025-64253 · published 2025-12-16
Path traversal / file read in Health Check & Troubleshooting (1.7.1 and older)
- Affected
- 1.7.1 and older
- Fixed in
- no fix listed yet
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Path Traversal: '.../...//' vulnerability in WordPress.org Health Check & Troubleshooting health-check allows Path Traversal.This issue affects Health Check & Troubleshooting: from n/a through <= 1.7.1.
high 8.8 CVE-2022-47161 · published 2023-05-25
Cross-site request forgery (CSRF) in Health Check & Troubleshooting (1.5.1 and older)
- Affected
- 1.5.1 and older
- Fixed in
- 1.6.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in The WordPress.Org community Health Check & Troubleshooting plugin <= 1.5.1 versions.
Recent activity
- 2024-07-25 — latest release on wordpress.org (1.7.1).
- 2025-12-16 — Path traversal / file read disclosed (CVE-2025-64253), no fix listed yet.
- 2023-05-25 — Cross-site request forgery (CSRF) disclosed (CVE-2022-47161), fixed in 1.6.0.
Get an email when Health Check & Troubleshooting has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Health Check & Troubleshooting (health-check) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by WordPress.org (6 tracked)
Types found in this plugin: Path traversal and file read (1) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/health-check (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/health-check"><img src="https://laskyr.com/plugins/health-check/badge.svg" alt="Health Check & Troubleshooting vulnerability status"></a>