# CVE-2024-10903: Broken Link Checker < 2.4.2 - Admin+ SSRF

> Admin users can perform Server-Side Request Forgery attacks via unvalidated link URLs in the Broken Link Checker plugin.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2024
- **Updated:** 30 Dec 2024
- **Also known as:** GHSA-7jjg-gm2c-94v7

## What is CVE-2024-10903?

CVE-2024-10903 is a medium-severity server-side request forgery vulnerability in Unknown Broken Link Checker, published on 26 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Broken Link Checker WordPress plugin before 2.4.2 does not validate a the link URLs before making a request to them, which could allow admin users to perform SSRF attack, for example on a multisite installation.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Managewp Broken Link Checker.

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

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

## Is CVE-2024-10903 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10903 exists.

## Other vulnerabilities in Unknown Broken Link Checker

- [CVE-2023-23737](https://insights.sbomify.com/CVE-2023-23737/): WordPress MainWP Broken Links Checker Extension Plugin <= 4.0 is vulnerable to SQL Injection (critical 9.3)
- [CVE-2022-2438](https://insights.sbomify.com/CVE-2022-2438/): Broken Link Checker <= 1.11.16 - Authenticated (Admin+) PHAR Deserialization (high 7.2)
- [CVE-2019-16521](https://insights.sbomify.com/CVE-2019-16521/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-17207](https://insights.sbomify.com/CVE-2019-17207/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2022-3922](https://insights.sbomify.com/CVE-2022-3922/): Broken Link Checker < 1.11.20 - Admin+ Cross-Site Scripting (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10903 is a medium-severity server-side request forgery vulnerability in Unknown Broken Link Checker, published on 26 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10903 exists.

Affected product: Unknown Broken Link Checker. 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-10903/ (Markdown: https://insights.sbomify.com/CVE-2024-10903/index.md)
```

## Sources

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

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