WordPress RCE Flaw Draws Nearly 63,000 Attack Attempts in Just 24 Hours
WordPress Core RCE vulnerability triggers 63K attack attempts within 24 hours of patch release.
A high-severity remote code execution vulnerability in WordPress Core versions 4.7–7.1.3 (CVSS 8.1) sparked nearly 63,000 attack attempts within a single day of patch availability. The flaw lacks a CVE identifier and has drawn immediate exploitation interest from threat actors across the threat landscape.
AI summary of the linked source. Not reviewed by an editor. How this works
Run WordPress Core?
Get an email when a new story names WordPress Core, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonA high-severity remote code execution vulnerability in WordPress Core (CVSS 8.1) was actively exploited nearly 63,000 times within a single day of a patch being made available, underscoring how rapidly threat actors move once a vulnerability becomes public. The absence of a CVE identifier did not deter attackers, highlighting that organizations cannot rely solely on formal vulnerability identifiers to prioritize patching. Sites running unpatched WordPress versions 4.7–7.1.3 remained exposed during this critical window, demonstrating the real cost of delayed patch cycles. This incident reinforces that the time between patch release and patch application is one of the most dangerous periods in the vulnerability lifecycle.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Threat intelligence
Attack campaigns reach your sector, suppliers or software before your team hears about them.