# CVE-2026-90937: froxlor before 2.2.5 nginx/Apache Configuration Injection via subdomain redirect URL

> Authenticated users can inject newlines into subdomain redirect URLs to corrupt web server configurations, causing denial of service or response hijacking.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-c3p2-mj7v-5mrc, GHSA-r2fc-pw6p-x28w

## What is CVE-2026-90937?

CVE-2026-90937 is a critical code injection vulnerability in froxlor, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

froxlor versions before 2.2.5 fail to validate newline characters in subdomain redirect URLs, allowing authenticated customers to inject arbitrary nginx or Apache configuration directives. Attackers can supply URLs containing literal newlines that are written verbatim into vhost config files during cron rebuild, enabling web server configuration corruption, denial of service, or hijacking of HTTP responses across hosted domains.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

## Which versions are affected by CVE-2026-90937?


## How do I fix CVE-2026-90937?

No fix has been published for CVE-2026-90937 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-90937 being exploited?

There is no known exploitation of CVE-2026-90937 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90937 and fix it if it is affected.

What it is: CVE-2026-90937 is a critical code injection vulnerability in froxlor, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90937 in the wild and no public exploit code.

Affected product: froxlor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90937/ (Markdown: https://insights.sbomify.com/CVE-2026-90937/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90937
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90937
- OSV: https://osv.dev/vulnerability/CVE-2026-90937

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90937/
Summaries are generated and may contain mistakes; the official description above is the record.