Liquid Web incident

Security Advisory: WordPress XSS2Shell Vulnerability (CVE-2026-64638)

Notice Resolved View vendor source →

Liquid Web experienced a notice incident on August 8, 2026, lasting 26d. The incident has been resolved; the full update timeline is below.

Started
Aug 08, 2026, 01:24 PM UTC
Resolved
Sep 03, 2026, 01:53 PM UTC
Duration
26d
Detected by Pingoru
Aug 08, 2026, 01:24 PM UTC

Update timeline

  1. investigating Aug 08, 2026, 01:24 PM UTC

    A high-severity reflected XSS vulnerability, CVE-2026-64638, has been identified in the WordPress login interface. Exploitation requires a victim to visit a specially crafted URL and, under specific conditions, could potentially lead to PHP code execution. Impacted versions Impacted versions: WordPress 4.7 – 7.0.2 (every release on every branch) WordPress 4.6 and earlier — end of life, no patch available Fixed versions: WordPress 7.0.3 WordPress 6.9.6 WordPress 6.8.7 Equivalent minor releases on every remaining supported branch back to 4.7 Recommended Action Customers are strongly encouraged to update WordPress core and ensure automatic security updates are enabled where appropriate. Since exploitation requires user interaction, customers should also remain vigilant against phishing attempts and avoid clicking suspicious or unsolicited links. Customers with automatic security updates enabled should receive the applicable update automatically; however, we recommend verifying the currently running WordPress version. There is currently no reported evidence of widespread exploitation in the wild. We will continue to monitor the situation and provide further updates if required. If you need assistance or have any concerns, please contact our Support team.

  2. resolved Sep 03, 2026, 01:53 PM UTC

    The WordPress security vulnerability CVE-2026-64638 has been addressed in the latest WordPress security releases. Customers are encouraged to keep their WordPress installations updated to the latest available security release within their current supported branch. We have proactively contacted customers identified as running potentially affected WordPress versions and provided recommendations to update their installations. At this time, the incident has been resolved, and the related status page notification will be closed.