Anti HackerWordPress extension · Billminozzi
CVE-2023-50858
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 Bill Minozzi Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan.This issue affects Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan: from n/a through 4.34.
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 Bill Minozzi's WordPress security plugin suite (Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan). The plugin lacks proper anti-CSRF token validation on admin actions, allowing attackers to trick authenticated administrators into unknowingly modifying security settings or disabling protections.
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
Anti HackerWordPress extension
<= 4.34CVSS 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.
-
Confirm the plugin is installedLog in to WordPress admin, go to Plugins > Installed Plugins and look for 'Billminozzi Anti Hacker' or 'Anti Hacker' in the listAffected if The plugin appears in the installed plugins list
-
Identify the installed version numberOn the Plugins page, locate the Anti Hacker plugin and look for the version number displayed beneath the plugin name, or check the plugin's main PHP file (wp-content/plugins/anti-hacker/anti-hacker.php) for the 'Version' header in the plugin comment blockAffected if The version displayed is 4.34 or lower
-
Verify the plugin is activeIn the WordPress Plugins admin page, check if the Anti Hacker plugin shows as 'Active' (not just installed but currently enabled)Affected if The plugin is active and running version 4.34 or below
-
Check admin action handling (advanced)Inspect the plugin's admin PHP files for nonce verification - look for calls to wp_verify_nonce or check_admin_referer before processing state-changing admin actions in files like anti-hacker.php or within includes/admin/ foldersAffected if The plugin code lacks nonce verification on admin action handlers (form submissions, settings changes)
You are affected if the Billminozzi Anti Hacker plugin is installed, active, and running version 4.34 or lower, as these versions lack CSRF token validation on admin actions.
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 plugin to version 4.35 or later which implements nonce verification on all state-changing admin actions. If immediate update is not possible, review admin actions and implement nonce checks on form submissions and AJAX requests.
Fix this in Anti Hacker
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-2023-50858 — 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-2023-50858 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