CVE-2026-67399

9.3

WebPros · WHMCS

WHMCS is vulnerable to deserialization of untrusted data, allowing remote unauthenticated attackers to execute arbitrary code on the underlying system.

Executive summary

A critical deserialization vulnerability in WebPros WHMCS allows unauthenticated remote code execution, posing an extreme risk to server integrity.

Vulnerability

The application improperly handles deserialization of untrusted data (CWE-502). This flaw allows an unauthenticated remote attacker to inject malicious serialized objects, resulting in arbitrary code execution with the privileges of the web application.

Business impact

The ability for an unauthenticated attacker to execute arbitrary code represents the highest level of system compromise. A successful exploit could lead to full server takeover, theft of customer billing data, or the deployment of ransomware within the hosting environment. Given the CVSS score of 9.3, this vulnerability demands immediate attention to prevent catastrophic business disruption.

Remediation

Immediate Action: Update WebPros WHMCS installations immediately to version 9.0.8 or 8.13.7, as specified in the vendor security advisory.

Proactive Monitoring: Review web server access logs for anomalous POST requests containing serialized object patterns or unexpected characters that may indicate exploitation attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block suspicious serialized data payloads, which may provide temporary protection while the patching process is completed.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

The critical nature of this vulnerability cannot be overstated. Because this flaw is exploitable by an unauthenticated attacker and enables arbitrary code execution, administrators must prioritize applying the provided patches across all WHMCS instances immediately. Delaying these updates leaves critical infrastructure exposed to potential full system compromise.

More WebPros CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources

Originally found and disclosed by azizk (@realazizk), per the CVE Program record.