dbcve.org
E Logbook With Health Monitoring System For Covid 19Application · Emiloi

CVE-2025-10118

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
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
Public exploit 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 security vulnerability has been detected in itsourcecode E-Logbook with Health Monitoring System for COVID-19 1.0. The affected element is an unknown function of the file /login.php. The manipulation of the argument Username leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used.

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

SQL injection vulnerability in the login.php file of itsourcecode E-Logbook with Health Monitoring System for COVID-19 1.0 allows remote attackers to inject malicious SQL queries through the Username parameter without proper input sanitization.

MitigationImplement parameterized queries or prepared statements for the Username parameter and all other user inputs in login.php to prevent SQL injection attacks.

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
E Logbook With Health Monitoring System For Covid 19Application
Affected:= 1.0

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. Locate the login.php file
    Search the web root directory for the login.php file typically found in the E-Logbook application folder
    Affected if login.php exists in the web application directory and is accessible via HTTP/HTTPS
  2. Confirm the application version
    Check for version information in the application's source files, README, or admin panel. Compare against version 1.0
    Affected if The installed version is Emiloi E Logbook With Health Monitoring System For Covid 19 version 1.0
  3. Examine login.php for SQL query handling
    Open login.php in a text editor and locate the SQL query that processes the Username parameter. Check if the query uses prepared statements/parameterized queries or concatenates user input directly into the SQL string
    Affected if The Username parameter is directly concatenated into the SQL query without using prepared statements or parameter binding
  4. Test for SQL injection vulnerability
    Send a malformed username value such as ' OR '1'='1 through the login form and observe if unexpected authentication behavior occurs or if error messages reveal database information
    Affected if The application exhibits unexpected behavior or returns database errors indicating unsanitized input is processed in the SQL query

The environment is affected if the E-Logbook COVID-19 Monitoring System version 1.0 is installed and the login.php file processes the Username parameter through unsanitized SQL queries.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for the Username parameter and all other user inputs in login.php to prevent SQL injection attacks.

Recommended fix Moderate confidence
  1. This vulnerability is in a closed-source COVID-19 monitoring application from itsourcecode.com version 1.0.
  2. No vendor patch, fixed version, or update has been identified in the available vulnerability data.
  3. The application should be decommissioned or replaced with a supported alternative.
  4. If continued use is required, implement strict network segmentation and WAF rules to block SQL injection attacks targeting /login.php
  5. Disable the application immediately if possible given the critical severity (CVSS 9.8) and public exploit availability.
Caveat No upgrade path available - vendor has not released any patches or newer versions for this product

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

Fix this in E Logbook With Health Monitoring System For Covid 19 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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