VulnerabilityPublished 4 Mar 2026

CVE-2025-59784: 2N Telekomunikace a.s 2N Access Commander · Log Injection

Affects 2N Telekomunikace a.s 2N Access CommanderSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.4.2 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.4.2

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade 2N Telekomunikace a.s 2N Access Commander to 3.4.2.

Affected software

Product	Affected	Fixed in
2N Telekomunikace a.s.2N Access Commander	Affected <3.4.2	Fixed in 3.4.2

AI-suggested

Upgrade 2N Access Commander to version 3.4.2 or later once the vendor releases a patch addressing this vulnerability.
If you cannot patch yet, restrict network access to the management interfaces of 2N Access Commander using firewalls, VPNs, or network segmentation to limit exposure.
Implement strict input validation and sanitization on any user-supplied data that may be logged, if customization or integration is possible.
Enhance log monitoring by deploying anomaly detection tools that can identify suspicious or malformed log entries indicative of injection attempts.
Maintain secure and immutable log storage solutions, such as write-once-read-many (WORM) systems or remote log aggregation, to prevent tampering after logging.
Conduct regular audits of log integrity and correlate logs with other security data sources to detect inconsistencies.
Educate security and IT teams about the risks of log injection and the importance of verifying log authenticity during investigations.
Follow vendor advisories closely for updates and apply patches promptly upon release.

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.

Impact

The primary impact of this vulnerability is on the integrity of log data generated by 2N Access Commander. Attackers exploiting this flaw can inject malicious entries into logs, potentially hiding their tracks or misleading security teams during incident response. This undermines trust in log data, which is essential for compliance, auditing, and forensic analysis. Although confidentiality and availability are not directly affected, the ability to tamper with logs can facilitate further attacks by obscuring evidence or triggering false alarms. Organizations relying on 2N Access Commander for physical access control or telecommunications infrastructure could face increased risk of undetected intrusions or insider threats. The lack of authentication requirements and ease of exploitation over the network increase the threat level, especially in environments with exposed management interfaces. However, the absence of known exploits in the wild and the medium CVSS score suggest a moderate but significant risk that should be addressed promptly.

Summary

CVE-2025-59784 is a vulnerability classified under CWE-117 (Improper Output Neutralization for Logs) affecting 2N Telekomunikace a.s.'s 2N Access Commander software on Linux platforms prior to version 3.4.2. The flaw arises because the software fails to properly sanitize or neutralize log entries, allowing an attacker to inject crafted input into log files. This can lead to log injection, tampering, or forging, which compromises the integrity of log data. Since logs are critical for security monitoring, auditing, and forensic investigations, manipulation can obscure malicious activities or create false evidence. The vulnerability is remotely exploitable over the network without requiring privileges or user interaction, as indicated by the CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N). The impact on confidentiality and availability is minimal, but the integrity of logs is affected (VI:L). No patches or exploits are currently publicly available, but the vendor has acknowledged the issue. The vulnerability primarily affects Linux deployments of 2N Access Commander, a software used for managing access control systems, often in enterprise and telecommunications environments.

CWE-117Improper Output Neutralization for Logs (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Logging (opens in a new tab)
Content Security Policy (opens in a new tab)
Application Logging Vocabulary (opens in a new tab)
OWASP ASVS 4.0.3
V7.3.1 (opens in a new tab)
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
Attack patterns
Audit Log Manipulation (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
Log Injection-Tampering-Forging (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

2n.com/en-GB/download/cve_2025_59784_acom_3_5_v1pdf (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Mar 2026, 15:48 UTC

WeaknessesCWE-117

Technical details

References

Community reviews

Related threats