CVE-2022-3880: The Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan WordPress plugi

Q: How do I fix CVE-2022-3880?

antihacker: upgrade to 4.20. Exact commands for each OS are on this page.

Q: Is CVE-2022-3880 being exploited?

CVE-2022-3880 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-3880 affect?

CVE-2022-3880 affects antihacker. Severity is medium (CVSS 6.5). The Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan WordPress plugin before 4.20 does not have proper authorisation and CSRF in an AJAX action, allowing any authenticated users, such as subscriber

Q: How urgent is CVE-2022-3880?

Priority 35/100. Public exploit reference

Routine

MEDIUM 6.5UPGRADE

CVE-2022-3880 is a medium-severity flaw (CVSS 6.5) affecting antihacker. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan WordPress plugin before 4.20 does not have proper authorisation and CSRF in an AJAX action, allowing any authenticated users, such as subscriber to call it and install and activate arbitrary plugins from wordpress.org

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-352, CWE-863
Published	2022-12-12
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: antihacker project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-12 18:15 UTCPublished CVE record published
2026-06-17 05:00 UTCUpdated Record last modified

antihacker project antihacker UPGRADE

Affected: < 4.20

Fixed in: 4.20

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy antihacker || rpm -q antihacker || antihacker --version

2. UPGRADE to 4.20 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade antihacker

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade antihacker

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-3880?

antihacker: upgrade to 4.20. Exact commands for each OS are on this page.

Is CVE-2022-3880 being exploited?

CVE-2022-3880 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-3880 affect?

CVE-2022-3880 affects antihacker. Severity is medium (CVSS 6.5). The Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan WordPress plugin before 4.20 does not have proper authorisation and CSRF in an AJAX action, allowing any authenticated users, such as subscriber

How urgent is CVE-2022-3880?

Priority 35/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs