WordPress RCE Flaw Targeted in Mass Attacks Within 24 Hours
A critical remote code execution flaw in WordPress Core drew nearly 63,000 attack attempts within a day of patch release. The vulnerability affects versions 4.7 through 7.1.3 and has a CVSS score of 8.1.
TL;DR
- Attackers targeted a newly patched WordPress Core RCE flaw within 24 hours.
- Nearly 63,000 exploitation attempts were recorded by threat monitoring systems.
- The flaw impacts versions 4.7 to 7.1.3 and scores 8.1 on the CVSS scale.
- No CVE ID has been assigned yet, but patches are available.
- Organizations using affected versions should update immediately.
Threat actors wasted no time exploiting a high-severity remote code execution (RCE) vulnerability in WordPress Core after patches became available. According to recent reports, nearly 63,000 attack attempts were detected in just 24 hours, targeting unpatched sites running versions 4.7 through 7.1.3.
The vulnerability, which currently lacks a CVE identifier, has been rated with a CVSS score of 8.1, indicating a high level of severity. This rapid exploitation highlights the ongoing risks organizations face when delays occur in applying security updates, especially for widely used platforms like WordPress.
Vulnerability Details
- Impacts WordPress Core versions 4.7 through 7.1.3
- CVSS score of 8.1 classifies it as a high-severity issue
- Enables remote code execution on affected sites
- No official CVE assigned at the time of reporting
- Patched shortly before active exploitation began
Security Recommendations
- Immediately update WordPress installations to the latest version
- Monitor server logs for signs of compromise or unusual activity
- Implement web application firewalls (WAFs) to filter malicious traffic
- Review access controls and disable unused plugins or themes
- Subscribe to WordPress security advisories for real-time updates
Sources
Sources
Security email updates
One digest email when we publish new security articles (TL;DR plus links to read more). Unsubscribe anytime from the message footer. See our Privacy Policy.