CVE-2025-59783: API endpoint for user synchronization in 2N Access Commander version 3.4.1 did not have a sufficient input val

Q: How do I fix CVE-2025-59783?

access commander: upgrade to 3.4.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-59783 being exploited?

CVE-2025-59783 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-59783 affect?

CVE-2025-59783 affects access commander. Severity is high (CVSS 7.2). 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 privi

This month

HIGH 7.2UPGRADE

CVE-2025-59783 is a high-severity flaw (CVSS 7.2) affecting access commander. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-78
Published	2026-03-04
Last modified	2026-06-17

Publisher (CNA): 2N · Vendor: 2n

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-04 16:16 UTCPublished CVE record published
2026-06-17 09:46 UTCUpdated Record last modified

2n access commander UPGRADE

Affected: < 3.4.2

Fixed in: 3.4.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy access-commander || rpm -q access-commander || access-commander --version

2. UPGRADE to 3.4.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade access-commander

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade access-commander

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-59783?

access commander: upgrade to 3.4.2. Exact commands for each OS are on this page.

Is CVE-2025-59783 being exploited?

CVE-2025-59783 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-59783 affect?

CVE-2025-59783 affects access commander. Severity is high (CVSS 7.2). 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 privi

How urgent is CVE-2025-59783?

Priority 40/100. High severity

Related CVEs

CVE-2025-59787 MEDIUM 6.5 UPGRADE 2N Access Commander application version 3.4.2 and prior returns HTTP 500 Internal Server Error responses when
CVE-2025-59786 CRITICAL 9.8 UPGRADE 2N Access Commander version 3.4.2 and prior improperly invalidates session tokens, allowing multiple session c
CVE-2025-59785 HIGH 7.2 UPGRADE Improper validation of API end-point in 2N Access Commander version 3.4.2 and prior allows attacker to bypass
CVE-2025-59784 HIGH 7.2 UPGRADE 2N Access Commander version 3.4.1 and prior is vulnerable to log pollution
CVE-2024-47255 MEDIUM 4.7 UPGRADE In 2N Access Commander versions 3.1.1.2 and prior, a local attacker can escalate their privileges in the syste

References

← Back to latest CVEs