dbcve.org
Access CommanderApplication · 2n

CVE-2025-59787

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-04
Fix available
A fix is available. Upgrade to 3.5 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The 2N Access Commander application versions 3.4.2 and prior returns HTTP 500 Internal Server Error responses when receiving malformed or manipulated HTTP requests, indicating improper handling of invalid input. This input validation failure could lead to information disclosure through verbose error messages or availability disruptions from repeated malformed requests.

MitigationUpgrade to a version newer than 3.4.2 if available, implement robust input validation and error handling to return appropriate error codes without exposing sensitive system information.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Access CommanderApplication
Affected:< 3.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify 2N Access Commander is installed
    Check for the presence of 2N Access Commander on the system by looking for its installation directory, service, or by querying running processes for 'Access Commander' or '2n' related processes.
    Affected if The application is installed and running on the system
  2. Determine installed version
    Check the version of 2N Access Commander by examining the application GUI, about section, or checking installed files for version metadata. Compare the found version against the affected range of versions prior to 3.5 (including 3.4.2 and earlier).
    Affected if The installed version is 3.4.2 or any version prior to 3.5
  3. Confirm HTTP interface is accessible
    Verify that the 2N Access Commander web interface is network-accessible by attempting to reach its HTTP/HTTPS port (typically port 80/443 or the configured web service port) from the network.
    Affected if The HTTP management interface is exposed and reachable over the network
  4. Test for verbose 500 error responses
    Send a malformed or intentionally invalid HTTP request to the web interface (such as requests with malformed headers, invalid URL encoding, or unexpected payload) and observe the HTTP response code and body.
    Affected if The application returns HTTP 500 Internal Server Error with detailed error information that could disclose sensitive system details

You are affected if 2N Access Commander version 3.4.2 or earlier is installed and its HTTP interface is accessible, as this version returns verbose 500 error messages that could disclose information when receiving malformed requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.5 or later
Fixed in 3.5
Interim mitigation

Upgrade to a version newer than 3.4.2 if available, implement robust input validation and error handling to return appropriate error codes without exposing sensitive system information.

Recommended fix Moderate confidence

3.5 or later

  1. 1. Identify all 2N Access Commander instances in the environment
  2. 2. Check the current version of each instance (version 3.4.2 or prior is affected)
  3. 3. Plan an upgrade to version 3.5 or later following standard upgrade procedures
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Apply the upgrade to production instances
  6. 6. Verify the fix by sending malformed or manipulated requests and confirming proper error handling (not HTTP 500)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Access Commander Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59787 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59787 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data