Quick answers
- Is CVE-2026-100717 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100717 being exploited in the wild.
- How severe is CVE-2026-100717?
- Critical severity, with a CVSS score of 9.9, published 26 September 2026.
- Which products and versions are affected?
- Froxlor 2.3.10 and earlier.
- Is there a fix for CVE-2026-100717?
- A patch was published on 2026-09-26: Fixed in version 2.3.12 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100717 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-100717?
- Check whether you run Froxlor 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
The Validate::validateUrl function checks only the path, query, and fragment URL components for CRLF sequences but fails to inspect the userinfo (user:pass@) component returned by parse_url. An attacker supplies a subdomain redirect URL with newline characters encoded in the userinfo portion (e.g., http://user%0amalicious%0a@evil.com/), which passes validation and is written verbatim into the generated vhost configuration. When froxlor regenerates and reloads web server config as root, the injected directives execute with full privilege.
Affected products
- froxlor froxlor 2.3.10 and earlier
Timeline
- 2026-09-26: disclosed: Published as GHSA-gxx3-hwjc-h2gp
- 2026-09-26: patched: Fixed in version 2.3.12