Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-3046: SQL Injection in itsourcecode E-Logbook with Health Monitoring System for COVID-19

0
Medium
VulnerabilityCVE-2026-3046cvecve-2026-3046
Published: Tue Feb 24 2026 (02/24/2026, 00:32:07 UTC)
Source: CVE Database V5
Vendor/Project: itsourcecode
Product: E-Logbook with Health Monitoring System for COVID-19

Description

A security vulnerability has been detected in itsourcecode E-Logbook with Health Monitoring System for COVID-19 1.0. This vulnerability affects unknown code of the file /check_profile_old.php. The manipulation of the argument profile_id leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/03/2026, 20:37:19 UTC

Technical Analysis

CVE-2026-3046 identifies a SQL injection vulnerability in the itsourcecode E-Logbook with Health Monitoring System for COVID-19 version 1.0. The vulnerability is located in the /check_profile_old.php script, specifically in the handling of the profile_id parameter. Due to insufficient input validation or sanitization, an attacker can craft malicious SQL queries that are executed by the backend database. This flaw allows remote attackers to manipulate database queries without requiring authentication or user interaction, which can lead to unauthorized data disclosure, data modification, or denial of service conditions. The vulnerability has a CVSS 4.0 base score of 6.9, reflecting medium severity with network attack vector, low attack complexity, and no privileges or user interaction needed. The vulnerability affects the confidentiality, integrity, and availability of the system's data to a limited extent. No official patches or fixes have been linked yet, and no exploits have been observed in the wild, but the public disclosure increases the risk of exploitation attempts. The affected product is specifically used for COVID-19 health monitoring, making the data sensitive and critical for public health operations. The vulnerability underscores the importance of secure coding practices, especially in healthcare-related software handling sensitive personal health information.

Potential Impact

The exploitation of this SQL injection vulnerability can lead to unauthorized access to sensitive health data related to COVID-19 monitoring, potentially exposing personal health information of individuals. Attackers could manipulate or delete records, undermining the integrity of health monitoring data, which could disrupt public health responses and decision-making. The availability of the system could also be affected if attackers execute queries that cause denial of service or crash the database. Given the nature of the data, confidentiality breaches could have legal and reputational consequences for affected organizations. Healthcare providers and public health authorities relying on this system may face operational disruptions and loss of trust. Although the vulnerability requires no authentication or user interaction, the scope is limited to deployments of this specific software version, which may restrict widespread impact. However, the public disclosure of the exploit code increases the likelihood of opportunistic attacks, especially in regions with less mature cybersecurity defenses.

Mitigation Recommendations

Organizations should immediately audit their use of the itsourcecode E-Logbook with Health Monitoring System for COVID-19 version 1.0 and identify affected instances. Since no official patch is currently linked, implement the following mitigations: 1) Apply input validation and parameterized queries or prepared statements in the /check_profile_old.php script to prevent SQL injection. 2) Employ web application firewalls (WAFs) with rules targeting SQL injection patterns, especially on the profile_id parameter. 3) Restrict database user permissions to the minimum necessary to limit the impact of potential injection attacks. 4) Monitor logs for suspicious query patterns or repeated access attempts targeting the vulnerable parameter. 5) If possible, upgrade to a newer, patched version of the software once available or consider alternative secure solutions. 6) Conduct regular security assessments and penetration testing focused on injection vulnerabilities. 7) Educate developers and administrators on secure coding and configuration practices to prevent similar issues in future deployments.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-02-23T17:30:46.406Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699cf533be58cf853bf604f5

Added to database: 2/24/2026, 12:47:47 AM

Last enriched: 3/3/2026, 8:37:19 PM

Last updated: 4/9/2026, 4:52:03 PM

Views: 53

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses