Quick answers
- Is CVE-2026-110799 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110799 being exploited in the wild.
- How severe is CVE-2026-110799?
- Critical severity, with a CVSS score of 9.8, published 30 October 2026.
- Which products and versions are affected?
- Vvveb prior to 1.0.8.7.
- Is there a fix for CVE-2026-110799?
- Yes: fixed in 1.0.8.7. Until then: Enforce strict input type validation on all authentication parameters using is_string() or is_scalar() checks before processing password reset requests, and ensure the database query layer does not interpret untrusted array values as query operators. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110799 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-110799?
- Check whether you run Vvveb 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.
How to fix
- Fixed in: 1.0.8.7
Enforce strict input type validation on all authentication parameters using is_string() or is_scalar() checks before processing password reset requests, and ensure the database query layer does not interpret untrusted array values as query operators.
Technical details
The vulnerability is an authentication bypass in the password reset flow caused by insufficient input type validation on the user and token GET parameters. An attacker can supply PHP array parameters (user[] and token[] instead of scalar strings) to bypass the lookup validation, allowing unauthorized access to the password reset form. This leads to full account takeover by enabling attackers to set arbitrary passwords for any user account.
Affected products
- Vvveb Vvveb prior to 1.0.8.7
Timeline
- 2026-10-29: disclosed
- 2026-10-30: advisory