LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-2438 affects the WordPress Broken Link Checker plugin through version 1.11.16. An already-authenticated administrator could abuse unsafe PHP deserialization if they can upload a crafted file and a usable object chain exists. This is serious for compromised or overly broad admin accounts, but it is not a drive-by unauthenticated issue.

Executive priority

Prioritize remediation where WordPress admin access is shared, weakly protected, or exposed to contractors. The vulnerability requires admin privileges, but successful abuse could have full site impact. Treat it as a high-priority hardening item, especially on revenue, lead-generation, or customer-facing sites.

Technical view

The flaw is CWE-502 deserialization of untrusted input through the $log_file value. A PHAR wrapper can trigger PHP object deserialization, potentially leading to arbitrary object behavior when a POP chain is present. Wordfence rates it CVSS 7.2 high with network access, low complexity, high privileges, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress installations running Broken Link Checker 1.11.16 or older. Practical risk depends on admin account security, whether an attacker can upload the required serialized payload file, and whether the environment contains a usable PHP object chain.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires authenticated administrator-level access, successful payload upload, PHAR-based file handling, and a compatible object chain, making this mainly a post-admin-compromise escalation or impact-amplification risk.

Researcher notes

The source bundle identifies a PHAR deserialization sink tied to $log_file and cites a WordPress plugin changeset. Do not assume unauthenticated exploitation. Key unknowns from the bundle are observed exploitation, exact fixed release naming, and environment-specific POP chain availability.

Mitigation direction

  • Upgrade Broken Link Checker to a vendor-supported version later than 1.11.16.
  • If upgrade timing is uncertain, check WordPress and vendor guidance before relying on workarounds.
  • Remove the plugin where it is not business-critical.
  • Restrict WordPress administrator access and require strong multifactor authentication.
  • Review administrator file upload permissions and plugin management access.

Validation and detection

  • Inventory all WordPress sites for Broken Link Checker installations.
  • Confirm installed plugin versions and flag 1.11.16 or older.
  • Review admin account activity for unexpected logins, uploads, or plugin changes.
  • Check web logs for unusual plugin file access around admin sessions.
  • Verify remediation in staging before production rollout.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-2438 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-2438Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wpmudevBroken Link Checker0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.