# CVE-2022-2438: Broken Link Checker <= 1.11.16 - Authenticated (Admin+) PHAR Deserialization

> Authenticated administrators can achieve arbitrary code execution via PHAR deserialization in the Broken Link Checker WordPress plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-3pxc-92w9-cmx7

## What is CVE-2022-2438?

CVE-2022-2438 is a high-severity unsafe deserialization vulnerability in wpmudev Broken Link Checker, published on 6 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Broken Link Checker plugin for WordPress is vulnerable to deserialization of untrusted input via the '$log_file' value in versions up to, and including 1.11.16. This makes it possible for authenticated attackers with administrative privileges and above to call files using a PHAR wrapper that will deserialize the data and call arbitrary PHP Objects that can be used to perform a variety of malicious actions granted a POP chain is also present. It also requires that the attacker is successful in uploading a file with the serialized payload.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2022-2438?

It affects 1 product.


Products: Managewp Broken Link Checker.

## How do I fix CVE-2022-2438?

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

## Is CVE-2022-2438 being exploited?

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

## Other vulnerabilities in wpmudev 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-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)
- [CVE-2024-10903](https://insights.sbomify.com/CVE-2024-10903/): Broken Link Checker < 2.4.2 - Admin+ SSRF (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2438 and fix it if it is affected.

What it is: CVE-2022-2438 is a high-severity unsafe deserialization vulnerability in wpmudev Broken Link Checker, published on 6 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2438 in the wild and no public exploit code.

Affected product: wpmudev 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-2022-2438/ (Markdown: https://insights.sbomify.com/CVE-2022-2438/index.md)
```

## Sources

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

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