Radar sectionsDatabase
Check my site
WordPress plugin

Health Check & Troubleshooting <= 1.5.1 — Cross-Site Request Forgery via health_check_troubleshoot_get_captures

CVE-2022-47161Published · Updated

Action summary

Affected: ≤1.5.1Update to 1.6.0 or newer

All remediation steps
Severity
Medium6.3
CVSS
6.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:U Scope
Unchanged
C:L Confidentiality
Low
I:L Integrity
Low
A:L Availability
Low
Weakness
CWE-352 CSRF
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Health Check & Troubleshooting health-check

  1. Affected≤ 1.5.1
  2. Patched in1.6.0

Update to 1.6.0 or newer.

You are affected if you run ≤ 1.5.1. Version 1.6.0 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Health Check & Troubleshooting.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 1.6.0, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Health Check & Troubleshooting to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Muhammad Daffa.

The Health Check & Troubleshooting plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.1. This is due to missing or incorrect nonce validation on the health_check_troubleshoot_get_captures function. This makes it possible for unauthenticated attackers to enable or disable plugins and themes, dismiss notices, or disable troubleshooting mode when the site is in troubleshooting mode via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Health Check & Troubleshooting

All 5
More vulnerabilities in Health Check & Troubleshooting
SeverityVulnerabilityCVEPublished
Low2.7Authenticated (Admin+) Path Traversal
≤1.7.1No patch available
CVE-2025-64253
Medium4.3Path Traversal
≤1.2.3Update to 1.2.4
—
High8.0Cross-Site Request Forgery
≤1.2.3Update to 1.2.4
—
High8.8Missing Authorization Checks
≤1.2.3Update to 1.2.4
—

Same weakness (CSRF)

All CSRF
Other CSRF vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 6.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?