Skip to main content
VulnerabilityPublished

CVE-2025-59785: 2N Telekomunikace a.s 2N Access Commander · – Improper Validation of Syntactic Correctness

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

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.5 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

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 29 Oct 2026.

What to do

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

Affected software

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

AI-suggested

To mitigate CVE-2025-59785, organizations should first verify if they are running 2N Access Commander version 3.4.2 or earlier and plan to upgrade to a fixed version once available. In the absence of an official patch, organizations should restrict administrator access strictly, enforcing strong credential management and multi-factor authentication to reduce the risk of credential compromise. Audit and monitor all administrative activities related to backup management to detect any anomalous behavior. Implement network segmentation and access controls to limit exposure of the Access Commander API endpoints to trusted networks and personnel only. Additionally, consider encrypting backup files using external tools or processes independent of the Access Commander password policy to ensure backup data remains protected even if the product's encryption policy is bypassed. Regularly review backup encryption policies and conduct penetration testing to validate the effectiveness of controls. Finally, maintain up-to-date incident response plans to quickly address any potential exploitation attempts.

Description

Improper validation of API end-point in 2N Access Commander version 3.4.2 and prior allows attacker to bypass password policy for backup file encryption. This vulnerability can only be exploited after authenticating with administrator privileges.

References

Community reviews

Loading reviews…