dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-4170

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
A weakness has been identified in Topsec TopACM 3.0. Affected by this vulnerability is an unknown functionality of the file /view/systemConfig/management/nmc_sync.php of the component HTTP Request Handler. Executing a manipulation of the argument template_path can lead to os command injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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 · high confidence

Critical OS command injection vulnerability in Topsec TopACM 3.0 allows remote attackers to execute arbitrary operating system commands by manipulating the template_path parameter in the /view/systemConfig/management/nmc_sync.php HTTP request handler. The vulnerability has a CVSS score of 9.8 and public exploits are available.

MitigationSince the vendor did not respond to disclosure, implement compensating controls such as web application firewall rules to block malicious template_path payloads, restrict network access to the management interface, and consider disabling the affected nmc_sync.php functionality until an official patch is available.

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

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
High
Integrity
High
Availability
High

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

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. Confirm Topsec TopACM installation
    Locate Topsec TopACM installation directories or check running services for TopACM. Common paths may include /usr/local/topsec/, /opt/topsec/, or check service processes for topacm-related binaries.
    Affected if Topsec TopACM is not installed on the system
  2. Identify installed TopACM version
    Check version files, about pages, or admin interfaces for the TopACM version number. Compare against the affected version 3.0.
    Affected if The installed version is TopACM 3.0 and the version cannot be determined or is 3.0
  3. Locate vulnerable PHP script
    Search for the file nmc_sync.php in the web root directory under the path /view/systemConfig/management/. Common web root locations: /var/www/html/, /usr/local/apache/htdocs/, or application document root.
    Affected if The file /view/systemConfig/management/nmc_sync.php exists on the server
  4. Verify management interface accessibility
    Check network configuration and web server access controls to determine if the /view/systemConfig/ path is accessible from network segments. Review firewall rules and web server configuration for the management interface.
    Affected if The management interface endpoint is exposed and reachable over the network
  5. Confirm command injection parameters
    Review HTTP access logs for requests to nmc_sync.php containing the template_path parameter. Inspect any observed requests for suspicious command characters like ; | & $ or backticks.
    Affected if Historical or current HTTP requests to nmc_sync.php with template_path parameter containing command injection payloads are present in logs

A system is affected if Topsec TopACM version 3.0 is installed with the nmc_sync.php script accessible on the network, as the vulnerability allows OS command execution through the template_path parameter in that specific PHP handler.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor did not respond to disclosure, implement compensating controls such as web application firewall rules to block malicious template_path payloads, restrict network access to the management interface, and consider disabling the affected nmc_sync.php functionality until an official patch is available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4170 — 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-2026-4170 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