Quick answers
- Is CVE-2026-73695 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73695 being exploited in the wild.
- How severe is CVE-2026-73695?
- Critical severity, with a CVSS score of 9.8, published 2 November 2026.
- Which products and versions are affected?
- Control Web Panel CWP before 1.16.
- Is there a fix for CVE-2026-73695?
- Yes: fixed in CWP 1.16 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73695 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-73695?
- Check whether you run Control Web Panel CWP 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: CWP 1.16 and later
Technical details
The vulnerability exists in services/users/index.php where an attacker-supplied module name is concatenated directly into an include path without sanitization, allowlisting, or use of basename(). An attacker can supply directory traversal sequences (e.g., ../) in the module parameter to include arbitrary .php files from the local filesystem, resulting in local file inclusion (LFI). This requires network access to the vulnerable endpoint but no authentication, enabling remote code execution if writable .php files are accessible or information disclosure via sensitive file inclusion.
Affected products
- Control Web Panel CWP before 1.16
Timeline
- 2026-11-02: disclosed