# CVE-2025-3766: Login Lockdown & Protection <= 2.11 - Missing Authorization to Authenticated (Subscriber+) Arbitrary IP Whitelisting

> Authenticated subscribers can bypass IP restrictions by whitelisting arbitrary IPs due to missing capability checks in the Login Lockdown plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/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:** 7 May 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-v2x8-7qj6-pc6f

## What is CVE-2025-3766?

CVE-2025-3766 is a medium-severity missing authorization vulnerability in webfactory Login Lockdown & Protection, published on 7 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Login Lockdown & Protection plugin for WordPress is vulnerable to unauthorized nonce access due to a missing capability check on the ajax_run_tool function in all versions up to, and including, 2.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, to obtain a valid nonce that can be used to generate a global unlock key, which can in turn be used to add arbitrary IP address to the plugin allowlist. This can only by exploited on new installations where the site administrator hasn't visited the loginlockdown page yet.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-3766?


## How do I fix CVE-2025-3766?

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

## Is CVE-2025-3766 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3766 and fix it if it is affected.

What it is: CVE-2025-3766 is a medium-severity missing authorization vulnerability in webfactory Login Lockdown & Protection, published on 7 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3766 in the wild and no public exploit code.

Affected product: webfactory Login Lockdown & Protection. 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-2025-3766/ (Markdown: https://insights.sbomify.com/CVE-2025-3766/index.md)
```

## Sources

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

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