CVE-2022-2438

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.

Category

7.2
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.42%
Third-Party Advisory wordfence.com Third-Party Advisory wordfence.com
Affected: wpmudev Broken Link Checker
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2022-2438?
CVE-2022-2438 has been scored as a high severity vulnerability.
How to fix CVE-2022-2438?
To fix CVE-2022-2438, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-2438 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-2438 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-2438?
CVE-2022-2438 affects wpmudev Broken Link Checker.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.