CVE-2026-3046
Received Received - Intake
SQL Injection in itsourcecode E-Logbook /check_profile_old.php

Publication date: 2026-02-24

Last updated on: 2026-04-29

Assigner: VulDB

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-24
Last Modified
2026-04-29
Generated
2026-05-06
AI Q&A
2026-02-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
emiloi e-logbook_with_health_monitoring_system_for_covid-19 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-3046 is a critical SQL injection vulnerability found in itsourcecode E-Logbook with Health Monitoring System for COVID-19 version 1.0. The vulnerability exists in the file /check_profile_old.php, specifically through improper handling of the profile_id parameter.

This parameter can be manipulated with crafted input to inject malicious SQL commands, allowing attackers to remotely execute SQL injection attacks without requiring any authentication.

The root cause is the lack of input validation and improper handling of user-supplied data in SQL queries.


How can this vulnerability impact me? :

This vulnerability allows attackers to perform unauthorized database operations, including unauthorized database access, sensitive data leakage, data tampering, and potentially full system control.

It can also lead to service disruption, posing significant risks to system security and business continuity.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by testing the vulnerable endpoint /check_profile_old.php for SQL injection via the profile_id parameter.'}, {'type': 'paragraph', 'content': 'One detection method is to use automated SQL injection testing tools such as sqlmap targeting the vulnerable URL and parameter.'}, {'type': 'list_item', 'content': 'Example sqlmap command: sqlmap -u "http://target.com/check_profile_old.php" --data="profile_id=1" -p profile_id --technique=BEUSTQ --dbms=MySQL'}, {'type': 'list_item', 'content': 'Use Google dorking to identify potentially vulnerable targets by searching: inurl:check_profile_old.php'}, {'type': 'paragraph', 'content': 'A proof-of-concept time-based blind SQL injection test can be performed by injecting payloads that induce delays, such as using the MySQL SLEEP() function, to confirm vulnerability.'}] [1, 2]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing proper input validation and sanitization for the profile_id parameter to prevent SQL injection.

  • Use prepared statements and parameterized queries to separate SQL code from user input.
  • Apply strict input filtering to ensure profile_id only accepts expected formats, such as numeric values.
  • Minimize database user permissions by avoiding high-privilege accounts for routine database operations.
  • Conduct regular security audits and code reviews to identify and remediate vulnerabilities promptly.

If possible, replace the affected component or upgrade to a version that addresses the vulnerability, although no fixed versions are currently indicated.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart