Health Check \& TroubleshootingWordPress extension · WordPress
CVE-2022-47161
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in The WordPress.Org community Health Check & Troubleshooting plugin <= 1.5.1 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the WordPress Health Check & Troubleshooting plugin versions 1.5.1 and below allows attackers to trick authenticated administrators into performing unintended administrative actions, such as modifying plugin settings or triggering troubleshooting functions, without their knowledge or consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Health Check \& TroubleshootingWordPress extension
<= 1.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Health Check & Troubleshooting' to see the version number. Alternatively, access the main plugin file (health-check.php) and look for the 'Version' header comment, or use WP-CLI: `wp plugin list --name=health-check`Affected if The displayed version is 1.5.1 or lower
-
Verify plugin is activeConfirm the Health Check & Troubleshooting plugin is activated in the WordPress admin under Plugins > Installed Plugins. An inactive plugin typically cannot be exploited for CSRF against administrators.Affected if The plugin is currently activated and the version is 1.5.1 or lower
-
Identify state-changing administrative functionsExamine the plugin directory (wp-content/plugins/health-check) for PHP files containing form handlers, settings update logic, or troubleshooting action handlers. Look for POST or GET requests that modify plugin state without nonce verification.Affected if The plugin contains administrative functions (settings changes, troubleshooting triggers) that process requests without validating a nonce token and the version is 1.5.1 or lower
A user is affected if the Health Check & Troubleshooting plugin version is 1.5.1 or lower, is currently activated, and contains administrative forms or actions that lack anti-CSRF nonce validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Health Check & Troubleshooting plugin to a version beyond 1.5.1, which should include proper anti-CSRF nonce validation for all state-changing operations and administrative forms.
Fix this in Health Check \& Troubleshooting
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47161 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-47161 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data