Skip to main content
VulnerabilityPublished

CVE-2025-59783: 2N Telekomunikace a.s 2N Access Commander · OS Command Injection

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

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 3.4.2 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% 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:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

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

Affected software

ProductAffectedFixed in
2N Telekomunikace a.s.2N Access CommanderAffected
  • <3.4.2
Fixed in
  • 3.4.2

AI-suggested

Organizations should immediately restrict administrator access to the 2N Access Commander API endpoint, enforcing strong authentication and monitoring for suspicious activity. Implement network segmentation to limit exposure of the management interface to trusted hosts only. Apply strict input validation and sanitization on all API inputs if possible, or deploy web application firewalls (WAFs) with custom rules to detect and block command injection patterns. Since no official patches are available yet, coordinate with 2N Telekomunikace a.s. for updates and advisories. Conduct thorough audits of administrator accounts and credentials to prevent unauthorized access. Employ multi-factor authentication (MFA) for all privileged users. Monitor system logs and network traffic for indicators of compromise related to command injection attempts. Prepare incident response plans specific to physical access control system compromises. Finally, consider isolating or temporarily disabling the vulnerable synchronization feature if feasible until a patch is released.

Description

API endpoint for user synchronization in 2N Access Commander version 3.4.1 did not have a sufficient input validation allowing for OS command injection. This vulnerability can only be exploited after authenticating with administrator privileges.

References

Community reviews

Loading reviews…