CVE-2025-59787

CVE-2025-59787 is a medium-severity vulnerability in 2n Access Commander with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-703.

Key facts

Description

2N Access Commander application version 3.4.2 and prior returns HTTP 500 Internal Server Error responses when receiving malformed or manipulated requests, indicating improper handling of invalid input and potential security or availability impacts.

Frequently asked questions

What is CVE-2025-59787?
2N Access Commander application version 3.4.2 and prior returns HTTP 500 Internal Server Error responses when receiving malformed or manipulated requests, indicating improper handling of invalid input and potential security or availability impacts.
How severe is CVE-2025-59787?
CVE-2025-59787 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability low.
Is CVE-2025-59787 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-59787?
CVE-2025-59787 affects 2n Access Commander. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-59787?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-59787 have an EU (EUVD) identifier?
Yes. CVE-2025-59787 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-208280.
When was CVE-2025-59787 published?
CVE-2025-59787 was published on 2026-03-04 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in 2n Access Commander

All CVEs affecting 2n Access Commander →

Other CWE-703 vulnerabilities

Browse all CWE-703 vulnerabilities →