Attackers are already attempting to exploit a newly disclosed high-severity remote code execution flaw in WordPress Core, according to reporting cited in the source. For European businesses that rely on WordPress for corporate websites, content platforms or e-commerce operations, the development is a practical reminder that patch delays can quickly become a business risk.

What happened

The reported vulnerability affects WordPress Core versions 4.7 through 7.1.3 and has been described as a remote code execution issue with a CVSS score of 8.1. The source states that exploitation attempts surged shortly after patches became available, with nearly 63,000 attack attempts observed within a 24-hour period.

At the time of the source report, the flaw was described as not having a CVE identifier. The key operational point for businesses is that attackers appear to have moved quickly once patch information was available, reducing the time window for organisations that postpone updates.

Why it matters for European businesses

WordPress remains widely used across Europe for marketing sites, lead-generation platforms, publisher sites and online shops. A remote code execution flaw is especially serious because, if successfully exploited, it can potentially allow an attacker to run malicious code on a vulnerable server or website environment.

For businesses, that can create several risks:

• Website disruption: a compromised site may be taken offline, defaced or used to distribute malicious content.
• Data exposure: attackers may attempt to access customer, form or administrative data depending on the broader hosting setup.
• E-commerce impact: online stores could face service interruptions, reputational damage or incident response costs.
• Further compromise: a website breach can become an entry point into connected systems, administrator accounts or third-party services.

For regulated organisations, a compromised public-facing website may also trigger internal security escalation, forensic review and possible data-protection assessment depending on what systems and data are involved.

Who may be affected

The most exposed organisations are those running vulnerable WordPress Core versions, especially if updates are not automated or if websites are maintained infrequently. This may include:

• SMEs using WordPress for their main company website
• e-commerce businesses using WordPress-based platforms
• marketing teams managing campaign landing pages on WordPress
• digital agencies responsible for client website maintenance
• IT teams overseeing self-hosted or lightly monitored web infrastructure

Risk may be higher where businesses use shared hosting, outdated plugins or themes, weak administrator controls, or lack continuous monitoring of web activity.

What companies should consider

• Confirm WordPress Core version: identify whether any business or client sites are running versions reported as affected.
• Apply available patches quickly: where updates have been released, reduce exposure by patching without unnecessary delay.
• Review staging and forgotten sites: older microsites, campaign pages and inactive subdomains are often missed during patch cycles.
• Check logs and security alerts: review recent web logs, admin activity and endpoint alerts for signs of suspicious requests or unauthorised changes.
• Verify backups and recovery plans: ensure clean backups exist and that website restoration procedures are tested.
• Harden administrator access: use strong authentication, limit privileged accounts and remove unused admin users.
• Coordinate with hosting and agency partners: confirm who is responsible for patching, monitoring and incident response across each WordPress property.

Businesses should avoid assuming that only large enterprises are targeted. Publicly accessible CMS platforms are routinely scanned and attacked at scale, and rapid patching is often the most effective first step when a core website vulnerability becomes active.