CVE-2026-67398
Unauthenticated access to WHMCS 2Checkout endpoint exposing customer data.
Is CVE-2026-67398 being exploited?
Not confirmed. CVE-2026-67398 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-67398?
CVE-2026-67398 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67398?
Yes. A fix has been recorded for CVE-2026-67398. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67398 affect?
CVE-2026-67398 affects WHMCS 8.13.0 - 8.13.7 (2Checkout gateway), WHMCS 9.0.0 - 9.0.7 (2Checkout gateway), WHMCS EOL versions from 4.5.0 with 2Checkout integration. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67398?
Update WHMCS to 8.13.8/9.0.8+; restrict payment endpoint, review logs, rotate exposed credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can retrieve WHMCS customer records via the 2Checkout payment endpoint, exposing personal/payment data.
Immediate action required
- affected>= 4.5.0 and <= 8.12.2
- affected>= 8.13.0 and < 8.13.8
- affected>= 9.0.0 and < 9.0.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.