CVE-2026-18937 Broken Link Checker CVE debrief

Who should care

WordPress site administrators using the Broken Link Checker plugin, especially those with public-facing sites or using plain permalinks, should be aware of this critical vulnerability. They should review their site configurations, verify plugin versions, and monitor for suspicious activity. Security teams and vulnerability management teams should prioritize patching and verify that compensating controls are in place for exposed systems.

Technical summary

The Broken Link Checker WordPress plugin before 2.4.12 does not limit which query variables it accepts from user input on sites using plain permalinks, allowing unauthenticated users to overwrite arbitrary PHP global variables, and to execute arbitrary code on the server when a classic (non-block) theme is active. This critical vulnerability affects WordPress site administrators using the Broken Link Checker plugin, especially those with public-facing sites or using plain permalinks. Immediate patching is recommended to prevent unauthenticated code execution.

Defensive priority

Critical vulnerability in Broken Link Checker WordPress plugin allows unauthenticated code execution; immediate patching recommended.

Recommended defensive actions

• Patch Broken Link Checker WordPress plugin to version 2.4.12 or later
• Restrict access to WordPress plugin management
• Monitor for suspicious activity on affected sites
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

Evidence from official CVE and NVD sources indicates critical vulnerability in Broken Link Checker WordPress plugin. Further analysis needed to determine affected scope, source-confidence limits, and what defenders should verify. Limited evidence suggests unauthenticated code execution risk on affected sites using plain permalinks and classic themes. Defenders should verify plugin versions, site configurations, and monitor for suspicious activity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.