Snort Report versions < 1.3.2 contains a remote command execution vulnerability in the nmap.php and nbtscan.php scripts. These scripts fail to properly sanitize user input passed via the target GET parameter, allowing attackers to inject arbitrary shell commands. Exploitation requires no authentication and can result in full compromise of the underlying system.
Security readout for executives and security teams
Plain-English summary
This is an unauthenticated remote command execution issue in legacy Snort Report web scripts. An attacker who can reach the affected pages could run operating-system commands as the web server user, creating a direct path to system compromise.
Executive priority
Treat this as urgent for any exposed Snort Report deployment. The business risk is not theoretical: unauthenticated remote command execution on a security monitoring host can undermine visibility and enable broader compromise.
Technical view
Snort Report versions before 1.3.2 are described as vulnerable to CWE-78 command injection in nmap.php and nbtscan.php through the target GET parameter. The CVSS 4.0 score is 10.0, with network access, no privileges, no user interaction, and high impact across confidentiality, integrity, and availability.
Likely exposure
Exposure is most likely in old or forgotten Snort Report installations, especially monitoring portals reachable from untrusted networks. The supplied affected-product metadata is limited and partly inconsistent, so teams should verify actual installed versions and reachable scripts.
Exploitation context
The source bundle includes public exploit references, but KEV is false and no cited source here confirms active exploitation. The risk remains severe because exploitation requires no authentication and can lead to full compromise of the host.
Researcher notes
Prioritize version confirmation, route exposure, and log review. The CVE record is newly published for an older issue, and the supplied metadata does not fully enumerate affected CPEs. Avoid assuming broader product impact beyond Snort Report before 1.3.2.
Mitigation direction
Upgrade Snort Report to version 1.3.2 or later, per the provided vendor patch reference.
Remove or isolate unsupported Snort Report deployments if they cannot be upgraded promptly.
Restrict access to Snort Report to trusted administrative networks only.
Monitor vendor and vulnerability advisories for any newer guidance or replacement recommendations.
Validation and detection
Inventory systems for Snort Report installations and record exact versions.
Identify whether nmap.php or nbtscan.php are present and reachable.
Review web logs for unexpected access to those scripts and target parameters.
Confirm the application is upgraded to 1.3.2 or no longer exposed.
Check external attack-surface scans for forgotten Snort Report portals.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.