In versions 2.3.10 and earlier, Validate::validateUrl rejects carriage return and line feed characters only in the path, query and fragment… (CVE-2026-100717)
In froxlor versions 2.3.10 and earlier, the URL validation function Validate::validateUrl does not properly inspect the userinfo component of URLs for carriage return and line feed characters. This allows an authenticated low-privilege user with subdomain creation rights to inject malicious payloads into the web server configuration. The injected directives can execute with root privileges, enabling server-wide impact such as response hijacking or local file reading. The vulnerability is fixed in version 2.3.12.
AI Analysis
Technical Summary
The vulnerability in froxlor affects versions 2.3.10 and earlier where Validate::validateUrl only rejects CR/LF characters in the path, query, and fragment parts of a URL but not in the userinfo component. An attacker with low-privilege authenticated access and subdomain creation rights can craft a subdomain redirect URL containing CR/LF payloads in the userinfo portion. This payload bypasses validation, survives IDNA encoding, and is injected verbatim into nginx or Apache virtual host configurations. Since froxlor regenerates and reloads the web server configuration as root, the attacker can inject arbitrary configuration directives, leading to server-wide compromise including response hijacking and local file access. The issue is resolved in froxlor version 2.3.12.
Potential Impact
An attacker with authenticated low-privilege access and subdomain creation rights can inject arbitrary web server configuration directives with root privileges. This can lead to server-wide compromise including hijacking HTTP responses and reading local files. The vulnerability has a high CVSS score of 9.9, indicating critical impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade froxlor to version 2.3.12 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by properly validating the userinfo component of URLs.
In versions 2.3.10 and earlier, Validate::validateUrl rejects carriage return and line feed characters only in the path, query and fragment… (CVE-2026-100717)
Description
In froxlor versions 2.3.10 and earlier, the URL validation function Validate::validateUrl does not properly inspect the userinfo component of URLs for carriage return and line feed characters. This allows an authenticated low-privilege user with subdomain creation rights to inject malicious payloads into the web server configuration. The injected directives can execute with root privileges, enabling server-wide impact such as response hijacking or local file reading. The vulnerability is fixed in version 2.3.12.
CVSS v3.1
Score 9.9critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in froxlor affects versions 2.3.10 and earlier where Validate::validateUrl only rejects CR/LF characters in the path, query, and fragment parts of a URL but not in the userinfo component. An attacker with low-privilege authenticated access and subdomain creation rights can craft a subdomain redirect URL containing CR/LF payloads in the userinfo portion. This payload bypasses validation, survives IDNA encoding, and is injected verbatim into nginx or Apache virtual host configurations. Since froxlor regenerates and reloads the web server configuration as root, the attacker can inject arbitrary configuration directives, leading to server-wide compromise including response hijacking and local file access. The issue is resolved in froxlor version 2.3.12.
Potential Impact
An attacker with authenticated low-privilege access and subdomain creation rights can inject arbitrary web server configuration directives with root privileges. This can lead to server-wide compromise including hijacking HTTP responses and reading local files. The vulnerability has a high CVSS score of 9.9, indicating critical impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade froxlor to version 2.3.12 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by properly validating the userinfo component of URLs.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-qjpj-j6j4-mcpf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-100717"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ab89bd7f7a7c54106941ff1
Added to database: 09/27/2026, 04:30:15 UTC
Last enriched: 09/27/2026, 04:40:27 UTC
Last updated: 09/28/2026, 01:47:40 UTC
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.