dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-30044

CRITICAL · 9.4 CVSS v4.0 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
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
In the endpoints "/cgi-bin/CliniNET.prd/utils/usrlogstat_simple.pl", "/cgi-bin/CliniNET.prd/utils/usrlogstat.pl", "/cgi-bin/CliniNET.prd/utils/userlogstat2.pl", and "/cgi-bin/CliniNET.prd/utils/dblogstat.pl", the parameters are not sufficiently normalized, which enables code injection.

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

Multiple CliniNET.prd CGI Perl scripts (usrlogstat_simple.pl, usrlogstat.pl, userlogstat2.pl, dblogstat.pl) are vulnerable to code injection due to insufficient parameter normalization. Attackers can inject malicious code through unsanitized input parameters in these CGI endpoints.

MitigationImplement strict input validation and parameter sanitization on all CGI scripts. Apply proper escaping/quoting for shell commands and use parameterized queries where applicable. Consider restricting or disabling these legacy CGI utilities if not actively used.

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
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate CliniNET CGI scripts on the system
    Search for the affected script files: usrlogstat_simple.pl, usrlogstat.pl, userlogstat2.pl, dblogstat.pl. Use commands like 'find / -name "usrlogstat*.pl" -o -name "dblogstat.pl" 2>/dev/null' or check common CGI directories such as /cgi-bin/, /usr/lib/cgi-bin/, or the application's cgi directory.
    Affected if Any of the four affected CGI scripts (usrlogstat_simple.pl, usrlogstat.pl, userlogstat2.pl, dblogstat.pl) are found on the system.
  2. Identify the web server serving CGI scripts
    Determine the web server in use (Apache, nginx, IIS, or other). Check configuration files: Apache typically uses httpd.conf or .conf files in /etc/apache2/, nginx uses nginx.conf, IIS uses IIS Manager. Identify if CGI execution is enabled.
    Affected if The web server has CGI module enabled and is configured to execute .pl scripts.
  3. Verify CGI script exposure via web
    Test if the identified CGI scripts are accessible over HTTP/HTTPS. Attempt to access each script via browser or curl, for example: 'curl -I http://target/cgi-bin/usrlogstat.pl'. Check web server access logs for requests to these endpoints.
    Affected if The affected CGI scripts are accessible as web endpoints (return HTTP 200 or other valid responses rather than 404).
  4. Review CGI script source for unsanitized parameters
    If access to the script files is available, examine the Perl code for direct use of CGI parameters in shell commands. Look for patterns like `system()`, `exec()`, `qx//`, or backtick operators that incorporate user-supplied input without proper sanitization. Search for unescaped variables used in command execution.
    Affected if The CGI scripts contain code that passes unsanitized input to shell execution functions (system, exec, qx, or backticks).
  5. Check input validation configuration
    Inspect the CGI scripts for input validation routines. Look for presence of taint mode (#!/usr/bin/perl -T), use of strict validation, or parameterized approaches. If the scripts lack these protections and accept parameters through the query string or POST data, the vulnerability is present.
    Affected if The CGI scripts lack input validation (no taint mode, no strict parameter checking) and accept query parameters that could be injected into shell commands.

A system is affected if any of the four CliniNET CGI scripts (usrlogstat_simple.pl, usrlogstat.pl, userlogstat2.pl, dblogstat.pl) are installed, exposed via web, and contain code that uses unsanitized input in shell execution contexts.

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

Implement strict input validation and parameter sanitization on all CGI scripts. Apply proper escaping/quoting for shell commands and use parameterized queries where applicable. Consider restricting or disabling these legacy CGI utilities if not actively used.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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