Skip to main content
VulnerabilityPublished Updated

CVE-2024-11197: Lock User Account (WordPress plugin) · Protection Mechanism Failure

Affects Lock User Account (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 4.2 Medium.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
babatechs Lock User AccountAffected
  • =0
Fixed in–

AI-suggested

Until an official fix is released, consider disabling application password logins or restricting API access for locked accounts as a temporary mitigation. Monitor vendor channels for updates and apply patches promptly once available.

Description

The Lock User Account plugin for WordPress is vulnerable to user lock bypass in all versions up to, and including, 1.0.5. This is due to permitting application password logins when user accounts are locked. This makes it possible for authenticated attackers, with existing application passwords, to interact with the vulnerable site via an API such as XML-RPC or REST despite their account being locked.

References

Community reviews

Loading reviews…