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.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-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- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/62fd472e-208b-48db-8f98-3d935c7a678c?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset/2757773/broken-link-checker/trunk/core/core.php?old=2605914&old_path=broken-link-checker%2Ftrunk%2Fcore%2Fcore.phpCVE reference
- https://www.wordfence.com/vulnerability-advisories/#CVE-2022-2438CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.
