# CVE-2020-10237: Froxlor Exposure of Sensitive Information to an Unauthorized Actor

> A race condition in the Froxlor installer allows local attackers to read sensitive configuration files containing passwords before permissions are set.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j9wr-mj69-cqmv

## What is CVE-2020-10237?

CVE-2020-10237 is a medium-severity vulnerability in n/a, published on 9 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Froxlor through 0.10.15. The installer wrote configuration parameters including passwords into files in /tmp, setting proper permissions only after writing the sensitive data. A local attacker could have disclosed the information if he read the file at the right time, because of _createUserdataConf in install/lib/class.FroxlorInstall.php.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

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

Products: Froxlor Froxlor.

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

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

## Is CVE-2020-10237 being exploited?

There is no known exploitation of CVE-2020-10237 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-10237 and fix it if it is affected.

What it is: CVE-2020-10237 is a medium-severity vulnerability in n/a, published on 9 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10237 in the wild and no public exploit code.

Affected packages and fixed versions:
- froxlor/froxlor (Packagist): affected all versions up to 0.10.15; no fix listed
- froxlor/froxlor (Packagist): affected all versions up to 0.10.15; 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-10237/ (Markdown: https://insights.sbomify.com/CVE-2020-10237/index.md)
```

## Sources

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

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