# CVE-2025-59784: Log Pollution - Control Characters Not Escaped

> Authenticated administrators can inject control characters into logs via API parameters, potentially corrupting log integrity.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-whr8-xqgw-9f74

## What is CVE-2025-59784?

CVE-2025-59784 is a medium-severity vulnerability in 2N Access Commander, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

2N Access Commander version 3.4.1 and prior is vulnerable to log pollution. Certain parameters sent over API may be included in the logs without prior validation or sanitisation.
This vulnerability can only be exploited after authenticating with administrator privileges.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

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

It affects 1 product.


Products: 2n Access Commander.

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

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

## Is CVE-2025-59784 being exploited?

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

## Other vulnerabilities in 2N Access Commander

- [CVE-2025-59783](https://insights.sbomify.com/CVE-2025-59783/): OS Command Injection over API (high 8.8)
- [CVE-2024-47253](https://insights.sbomify.com/CVE-2024-47253/): Path traversal in 2N Access Commander (high 7.2)
- [CVE-2024-47254](https://insights.sbomify.com/CVE-2024-47254/): Privilege escalation in 2N Access Commander (medium 6.3)
- [CVE-2025-59786](https://insights.sbomify.com/CVE-2025-59786/): Cookies are not Invalidated upon Logout and Password Change (medium 6.0)
- [CVE-2025-59785](https://insights.sbomify.com/CVE-2025-59785/): API - Insufficient Input Validation (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59784 is a medium-severity vulnerability in 2N Access Commander, published on 4 Mar 2026. 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-2025-59784 in the wild and no public exploit code.

Affected product: 2N Access Commander. 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-59784/ (Markdown: https://insights.sbomify.com/CVE-2025-59784/index.md)
```

## Sources

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

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