# CVE-2024-11197: Lock User Account <= 1.0.5 - User Lock Bypass

> Authenticated attackers with application passwords can bypass account locks to access APIs, undermining security controls in the Lock User Account WordPress plugin.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2024
- **Updated:** 8 Apr 2026

## What is CVE-2024-11197?

CVE-2024-11197 is a medium-severity authentication bypass vulnerability in babatechs Lock User Account, published on 21 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2024-11197?


## How do I fix CVE-2024-11197?

No fix has been published for CVE-2024-11197 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11197 being exploited?

There is no known exploitation of CVE-2024-11197 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11197 and fix it if it is affected.

What it is: CVE-2024-11197 is a medium-severity authentication bypass vulnerability in babatechs Lock User Account, published on 21 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11197 in the wild and no public exploit code.

Affected product: babatechs Lock User Account. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11197/ (Markdown: https://insights.sbomify.com/CVE-2024-11197/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11197
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11197
- OSV: https://osv.dev/vulnerability/CVE-2024-11197

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11197/
Summaries are generated and may contain mistakes; the official description above is the record.