# CVE-2025-11707: Login Lockdown & Protection <= 2.14 - IP Block Bypass

> Unauthenticated attackers can bypass IP blocks by generating valid unblock keys, allowing continued brute-force login attempts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-95hc-3vwp-3cjf

## What is CVE-2025-11707?

CVE-2025-11707 is a medium-severity vulnerability in webfactory Login Lockdown & Protection, published on 13 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Login Lockdown & Protection plugin for WordPress is vulnerable to IP Block Bypass in all versions up to, and including, 2.14. This is due to $unblock_key key being insufficiently random allowing unauthenticated users, with access to an administrative user email, to generate valid unblock keys for their IP Address. This makes it possible for unauthenticated attackers to bypass blocks due to invalid login attempts.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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


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

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

## Is CVE-2025-11707 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11707 is a medium-severity vulnerability in webfactory Login Lockdown & Protection, published on 13 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11707 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-11707/ (Markdown: https://insights.sbomify.com/CVE-2025-11707/index.md)
```

## Sources

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

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