# CVE-2025-54120: PCL Community Edition exposes login credentials in logs

> Attackers can obtain login credentials if users manually share local log files containing sensitive data from the Minecraft launcher.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jul 2025
- **Updated:** 23 Jul 2025
- **Also known as:** GHSA-f3rx-h3cv-696g

## What is CVE-2025-54120?

CVE-2025-54120 is a critical vulnerability in PCL-Community PCL2-CE, published on 23 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

PCL (Plain Craft Launcher) Community Edition is a Minecraft launcher. In PCL CE versions 2.12.0-beta.5 to 2.12.0-beta.9, the login credentials used during the third-party login process are accidentally recorded in the local log file. Although the log file is not automatically uploaded or shared, if the user manually sends the log file, there is a risk of leakage. This is fixed in version 2.12.0-beta.10.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-54120?


## How do I fix CVE-2025-54120?

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

## Is CVE-2025-54120 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54120 and fix it if it is affected.

What it is: CVE-2025-54120 is a critical vulnerability in PCL-Community PCL2-CE, published on 23 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-54120 in the wild and no public exploit code.

Affected product: PCL-Community PCL2-CE. 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-2025-54120/ (Markdown: https://insights.sbomify.com/CVE-2025-54120/index.md)
```

## Sources

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

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