Log corruption via unsanitized API parameters
Published Mar 4, 2026 · Updated Mar 4, 2026
Log injection in 2N Access Commander 3.4.1 and earlier allows remote authenticated users to corrupt logs through crafted API parameters. The API logging path copies certain parameter values into application logs without validation or neutralization before output. Administrator privileges are required, and exploitation can insert misleading entries or alter how log records are parsed.
Summary
What happened
Log injection in 2N Access Commander 3.4.1 and earlier allows remote authenticated users to corrupt logs through crafted API parameters. The API logging path copies certain parameter values into application logs without validation or neutralization before output. Administrator privileges are required, and exploitation can insert misleading entries or alter how log records are parsed.
The record
- CVE
- CVE-2025-59784
- Published
- Mar 4, 2026
- Updated
- Mar 4, 2026
- Vendor
- 2N
- Product
- 2N Access Commander
- Classifications
- CWE-117
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 4, 2026CVE publishedPublication date reported by the CVE source.
- Mar 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.4.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo