Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-2438: The Broken Link Checker plugin for WordPress is vulnerable to deserialization of untrusted input via the '$log

45
This month
HIGH 7.2UPGRADE

CVE-2022-2438 is a high-severity flaw (CVSS 7.2) affecting broken link checker. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance1.8% (top 22%)
CISA exploited listNo
WeaknessCWE-502
Published2022-09-06
Last modified2026-06-17
Publisher (CNA): Wordfence · Vendor: managewp

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

managewp broken link checker UPGRADE
Affected: < 1.11.17
Fixed in: 1.11.17
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy broken-link-checker || rpm -q broken-link-checker || broken-link-checker --version
2. UPGRADE to 1.11.17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade broken-link-checker
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade broken-link-checker
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-2438?

broken link checker: upgrade to 1.11.17. Exact commands for each OS are on this page.

Is CVE-2022-2438 being exploited?

CVE-2022-2438 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-2438 affect?

CVE-2022-2438 affects broken link checker. Severity is high (CVSS 7.2). 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 priv

How urgent is CVE-2022-2438?

Priority 45/100. High severity

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.