The September patch cycle brought an uncomfortable surprise for WHMCS administrators: an unauthenticated remote code execution flaw classified as critical. Two months later, unpatched installations are still a common sight.

What was fixed

WHMCS released versions 9.0.8 and 8.13.7 on September 3, 2026, addressing two separate vulnerabilities. Both were disclosed in vendor security advisories on the same day.

CVE-2026-67399 — Unauthenticated RCE

The nastier of the two. WHMCS describes it as a flaw in WHMCS 8.0.x and later “involving the submission of forged payloads without adequate restrictions.” Under the right conditions, an unauthenticated attacker — no login needed, no account required — can execute arbitrary code on the server hosting WHMCS, resulting in complete compromise of the installation and all its data.

WHMCS’s own advisory is notably sparse on technical details, which is typical when a patch is rushed out ahead of potential exploitation. Third-party CVE databases rate this at 9.3 on the CVSS 4.0 scale (Critical), with the attack vector marked as network, no authentication required, and no user interaction needed. The vendor has not published a CVSS score of its own and has not confirmed the specific exploitation technique beyond the “forged payloads” description.

There is no vendor-provided workaround for CVE-2026-67399. The only fix is upgrading to 9.0.8 or 8.13.7.

CVE-2026-67398 — Unauthenticated PII Disclosure

A separate flaw in the 2CheckOut payment gateway module, present since WHMCS 4.5.0. An unauthenticated user can retrieve client personal data — name, billing address, city, state, postal code, country, email, and phone number — via an endpoint that should require authorization but does not under specific conditions. This one was discovered and responsibly disclosed by researcher “boomerang.”

Third-party databases rate it at 8.2 (High) on the CVSS 4.0 scale and classify it as a missing authorization flaw; the vendor’s advisory does not use those exact terms but the description fits.

A temporary workaround exists for CVE-2026-67398: go to Configuration → System Settings → Payment Gateways and click Deactivate next to 2CheckOut. If you don’t use 2CheckOut as an active gateway, deactivate it now regardless of your patching timeline.

Who is affected

All WHMCS builds in the 8.x series before 8.13.7, and all 9.x builds before 9.0.8. The vendor’s advisory language on CVE-2026-67399 says “WHMCS 8.0.x and later,” which third-party sources confirm starts at 8.0.0. For CVE-2026-67398, the affected range starts at 4.5.0 — a release from many years ago — but the vendor is only patching supported versions (8.13.7 and 9.0.8).

If you’re running anything older than 8.13.7 or 9.0.8, assume you are vulnerable to both.

Upgrading

The standard upgrade path applies:

  1. Back up your database first. WHMCS upgrades run database migrations; there is no rolling back without a backup.
  2. Download the latest release from your WHMCS client area.
  3. Follow the official upgrade guide.
  4. Test on a staging server if you have one.

If you’re running WHMCS 7.x or earlier, you’re on an unsupported branch that receives no patches for either CVE. The vendor’s recommended path is to upgrade to 8.13.7 or 9.0.8.

One operational note: WHMCS instances are publicly discoverable by their fingerprints — the login page, default paths, and HTTP headers are distinctive. Automated scanners have been indexing exposed panels for years. The combination of discoverability and an unauthenticated RCE is exactly what mass exploitation campaigns look for.

What this means for kalfaoglu.net customers

kalfaoglu.net manages billing infrastructure on behalf of customers, so the WHMCS installation here is handled operationally and kept up to date. Customers who self-host WHMCS on a VPS or dedicated server provisioned through kalfaoglu.net need to check their own installations separately.

Check your version: Admin panel → Help → About WHMCS, or look at the footer of any page in the admin area. If you’re below 9.0.8 or 8.13.7, treat this as urgent — the September advisory is two months old and exploitation tooling tends to follow vendor disclosures quickly.

Sources