# CVE-2023-50256: Froxlor username/surname AND company field Bypass

> Attackers can bypass mandatory field validation in the registration form by leaving essential fields blank, allowing incomplete account creation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-625g-fm5w-w7w4

## What is CVE-2023-50256?

CVE-2023-50256 is a high-severity vulnerability in Froxlor, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Froxlor is open source server administration software. Prior to version 2.1.2, it was possible to submit the registration form with the essential fields, such as the username and password, left intentionally blank. This inadvertent omission allowed for a bypass of the mandatory field requirements (e.g. surname, company name) established by the system. Version 2.1.2 fixes this issue.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-50256?

2 open source packages ship an affected version, including froxlor/froxlor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `froxlor/froxlor` | Packagist | All versions | 2.1.2 |
| `froxlor/froxlor` | Packagist | All versions | 2.1.2 |

Products: Froxlor Froxlor.

## How do I fix CVE-2023-50256?

Upgrade froxlor/froxlor to 2.1.2 or later.

## Is CVE-2023-50256 being exploited?

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

## Other vulnerabilities in Froxlor

- [CVE-2026-41228](https://insights.sbomify.com/CVE-2026-41228/): Froxlor has Local File Inclusion via path traversal in API `def_language` parameter that leads to Remote Code Execution (critical 10.0)
- [CVE-2023-6069](https://insights.sbomify.com/CVE-2023-6069/): Improper Link Resolution Before File Access in froxlor/froxlor (critical 9.9)
- [CVE-2023-0671](https://insights.sbomify.com/CVE-2023-0671/): Code Injection in froxlor/froxlor (critical 9.9)
- [CVE-2023-3173](https://insights.sbomify.com/CVE-2023-3173/): Improper Restriction of Excessive Authentication Attempts in froxlor/froxlor (critical 9.8)
- [CVE-2023-1307](https://insights.sbomify.com/CVE-2023-1307/): Authentication Bypass by Primary Weakness in froxlor/froxlor (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50256 and fix it if it is affected.

What it is: CVE-2023-50256 is a high-severity vulnerability in Froxlor, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-50256 in the wild and no public exploit code.

Affected packages and fixed versions:
- froxlor/froxlor (Packagist): affected all versions; fixed in 2.1.2
- froxlor/froxlor (Packagist): affected all versions; fixed in 2.1.2

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-2023-50256/ (Markdown: https://insights.sbomify.com/CVE-2023-50256/index.md)
```

## Sources

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

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