Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan vulnerabilities
Plugin slug antihacker · 4 known vulnerabilities · latest disclosed 2024-02-27 · WordPress.org page
Every listed vulnerability has a fix. Version 4.53 or later is not affected by any of them. If your site runs an older version, update it.
0 of 4 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 6.5 | <= 4.51 | 4.52 | CVE-2024-1860 | 2024-02-27 | Advisory |
| Medium 4.3 | <= 4.52 | 4.53 | CVE-2024-1861 | 2024-02-27 | Advisory |
| Medium 4.3 | < 4.35 | 4.35 | CVE-2023-50858 | 2023-12-22 | Advisory |
| Medium 6.5 | <= 4.19 | 4.20 | CVE-2022-3880 | 2022-11-21 | Advisory |
Check if a site is affected
Enter a site address to see which version of Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan plugin safe to use?
All 4 known issues are fixed in current versions (4.53 or later). Keeping it updated is what matters.
How do I check which version of Disable Json API, Login Lockdown, XMLRPC, Pingback, Stop User Enumeration Anti Hacker Scan my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.