CVE-2026-96562 wpmudev CVE debrief

Who should care

WordPress administrators and users with the Broken Link Checker plugin installed should assess their exposure and prioritize updates or mitigations. Security teams monitoring WordPress installations should also be aware of this vulnerability and its potential impact.

Why it matters

CVE-2026-96562 allows unauthenticated attackers to execute arbitrary shortcodes in the Broken Link Checker plugin for WordPress. Defenders should prioritize updates or mitigations, especially if comment moderation workflows allow untrusted input. The vulnerability's impact and remediation require verification from official sources.

• Potential for unauthenticated attackers to execute arbitrary shortcodes, which could lead to various impacts depending on the shortcode used.
• Possible exploitation through comment moderation workflows, which may not be closely monitored.
• Execution of shortcodes via WP-Cron without further attacker interaction after comment approval.
• Requires verification of affected versions, exploitation, and remediation from official sources.

Technical summary

The Broken Link Checker plugin for WordPress is vulnerable to arbitrary shortcode execution due to inadequate validation before running do_shortcode. This allows unauthenticated attackers to execute arbitrary shortcodes by submitting comments with shortcode payloads, which are executed automatically via WP-Cron upon comment approval. Affected product deployments should be identified in managed environments, and defenders should prioritize updating or disabling the plugin, especially if comment moderation workflows allow untrusted input. Additional security measures, such as limiting comment posting to authenticated users or using a security plugin to detect suspicious activity, should be considered.

Defensive priority

Defenders should prioritize updating or disabling the Broken Link Checker plugin immediately, especially if comment moderation workflows allow untrusted input.

Recommended defensive actions

• Update the Broken Link Checker plugin to a version beyond 2.4.14.1.
• Disable the Broken Link Checker plugin if immediate update is not possible.
• Monitor comment moderation workflows for potential exploitation attempts.
• Implement additional security measures for WordPress installations, such as limiting comment posting to authenticated users or using a security plugin to detect suspicious activity.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• 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

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 6.5 and severity of MEDIUM. The Broken Link Checker plugin's vulnerability allows unauthenticated attackers to execute arbitrary shortcodes by submitting comments with shortcode payloads.

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.