# CVE-2020-29653: HTML Injection in Froxlor

> Attackers can inject arbitrary HTML into the login page via the customermail parameter, potentially stealing credentials or executing scripts.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j739-gw6q-f4c7

## What is CVE-2020-29653?

CVE-2020-29653 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Froxlor through 0.10.22 does not perform validation on user input passed in the customermail GET parameter. The value of this parameter is reflected in the login webpage, allowing the injection of arbitrary HTML tags.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2020-29653?

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 to 0.10.22 | None |
| `froxlor/froxlor` | Packagist | All versions to 0.10.22 | None |

Products: Froxlor Froxlor.

## How do I fix CVE-2020-29653?

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

## Is CVE-2020-29653 being exploited?

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

## Other vulnerabilities in n/a

- [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-2020-29653 and fix it if it is affected.

What it is: CVE-2020-29653 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-29653 in the wild and no public exploit code.

Affected packages and fixed versions:
- froxlor/froxlor (Packagist): affected all versions up to 0.10.22; no fix listed
- froxlor/froxlor (Packagist): affected all versions up to 0.10.22; no fix listed

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

## Sources

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

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