Missing AuthenticationWeakness · CWE-306

CVE-2025-30041

CRITICAL · 9.0 CVSS v4.0 Published 2025-08-27

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

95/100

Remediation priority · Urgent

No privileges Zero-click

Official description

NVD · unedited

The paths "/cgi-bin/CliniNET.prd/utils/userlogstat.pl", "/cgi-bin/CliniNET.prd/utils/usrlogstat.pl", and "/cgi-bin/CliniNET.prd/utils/dblogstat.pl" expose data containing session IDs.

Technical summary

dbcve analysis · high confidence

Three CGI scripts in the CliniNET healthcare application (userlogstat.pl, usrlogstat.pl, dblogstat.pl) are exposing session IDs in their output. This critical vulnerability allows unauthenticated attackers to harvest valid session identifiers and perform session hijacking attacks against authenticated users of the system.

MitigationImmediately disable or restrict access to the exposed CGI scripts until a vendor patch is obtained. Audit logs for any evidence of exploitation and consider forcing re-authentication for all users if session IDs may have been compromised.

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

CVSS breakdown

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:P/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?

dbcve checks

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

Identify installed CliniNET application and locate CGI scripts

Search the web server document root and CGI directories for the files userlogstat.pl, usrlogstat.pl, and dblogstat.pl. Common paths include /cgi-bin/, /htdocs/cgi-bin/, or the application's cgi directory.

Affected if Any of the three CGI scripts (userlogstat.pl, usrlogstat.pl, dblogstat.pl) exist on the system
Verify CGI scripts are web-accessible

Check the web server configuration (Apache httpd.conf, nginx config, or equivalent) to confirm the CGI directory containing these scripts is mapped to a URL endpoint accessible via HTTP/HTTPS.

Affected if The CGI scripts are served by the web server and reachable via HTTP/HTTPS requests without authentication
Test CGI script output for session ID exposure

Execute or request each CGI script (userlogstat.pl, usrlogstat.pl, dblogstat.pl) and inspect the output for any session identifiers, session tokens, or session keys. Look for patterns like sessionid=, SID=, PHPSESSID=, or similar session-related parameters in the response.

Affected if The CGI scripts return any session identifiers, session tokens, or session-related data in their output
Inspect web server access logs for CGI script requests

Review web server access logs (access_log, error_log) for any GET or POST requests to /userlogstat.pl, /usrlogstat.pl, or /dblogstat.pl. Check for patterns indicating unauthorized access.

Affected if There are logged requests to these CGI scripts, especially from unauthenticated or unexpected IP addresses
Check session configuration for exposure vectors

Review the application's session configuration files or session management settings to determine how session IDs are generated and whether the CGI scripts have legitimate need to handle session data.

Affected if The CGI scripts are configured to process or display session IDs when they should not have that capability

A system is affected if any of the three CGI scripts (userlogstat.pl, usrlogstat.pl, dblogstat.pl) exist, are web-accessible, and expose session identifiers in their output to unauthenticated users.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Immediately disable or restrict access to the exposed CGI scripts until a vendor patch is obtained. Audit logs for any evidence of exploitation and consider forcing re-authentication for all users if session IDs may have been compromised.

Have this fixed Scoped from the published advisory

Consultation6.0 h
Implementation4.0 h
Testing2.0 h
Review / QA2.0 h

14.0 hours of engineering $2,580

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

cert.pl
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-30041?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 9.0 Critical

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

A high-priority fix

Have this fixed 14 hrs · Moderate

Typical engagement from $2,580

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-30041 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References