Quick answers
- Is CVE-2026-67398 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67398 being exploited in the wild.
- How severe is CVE-2026-67398?
- Informational severity, published 4 September 2026.
- Which products and versions are affected?
- WHMCS 4.5.0 through 8.13.6, 9.0.0 through 9.0.7.
- Is there a fix for CVE-2026-67398?
- A patch was published on 2026-09-03: WHMCS 8.13.7 and 9.0.8 released with fixes Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67398 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-67398?
- Check whether you run WHMCS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A missing authorization vulnerability exists in the 2Checkout payment gateway module of WHMCS, where specific endpoints fail to properly authenticate requests before returning customer data. The vulnerability is accessible to unauthenticated users under certain conditions and allows retrieval of personally identifiable information (PII) such as client names, addresses, email, and phone numbers. The flaw affects WHMCS versions 4.5.0 through 8.13.6 and 9.0.0 through 9.0.7. Patches are available in WHMCS 8.13.7 and 9.0.8; as a temporary workaround, the 2Checkout payment gateway module can be deactivated in system settings.
Affected products
- WHMCS WHMCS 4.5.0 through 8.13.6, 9.0.0 through 9.0.7
Timeline
- 2026-09-03: disclosed
- 2026-09-03: patched: WHMCS 8.13.7 and 9.0.8 released with fixes