CVE-2026-3068
Received Received - Intake
SQL Injection in itsourcecode DMS /deluser.php Allows Remote Exploit

Publication date: 2026-02-24

Last updated on: 2026-04-29

Assigner: VulDB

Description
A weakness has been identified in itsourcecode Document Management System 1.0. This impacts an unknown function of the file /deluser.php. Executing a manipulation of the argument user2del can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-24
Last Modified
2026-04-29
Generated
2026-05-27
AI Q&A
2026-02-24
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
admerc document_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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.
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.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': 'CVE-2026-3068 is a critical SQL injection vulnerability in itsourcecode Document Management System version 1.0, specifically in the /deluser.php file.'}, {'type': 'paragraph', 'content': "The vulnerability arises because the application fails to properly sanitize or validate the 'user2del' parameter before using it in SQL queries. This allows attackers to inject malicious SQL code remotely without any authentication."}, {'type': 'paragraph', 'content': 'Exploitation techniques include boolean-based blind, error-based, and time-based blind SQL injections targeting MySQL databases, enabling attackers to manipulate SQL commands arbitrarily.'}] [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized database access, allowing attackers to view, modify, or delete sensitive data.

Attackers can gain full system control, disrupt services, and compromise the confidentiality, integrity, and availability of the system.

  • Unauthorized data leakage
  • Data tampering
  • Full system compromise
  • Service disruption

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 SQL injection vulnerability can be detected by testing the /deluser.php endpoint, specifically the 'user2del' parameter, for SQL injection flaws."}, {'type': 'paragraph', 'content': 'Example payloads to test include boolean-based blind, error-based, and time-based blind SQL injection techniques targeting MySQL databases.'}, {'type': 'list_item', 'content': "Boolean-based blind injection using RLIKE clause: user2del=111' RLIKE (SELECT (CASE WHEN (3036=3036) THEN 111 ELSE 0x28 END))--"}, {'type': 'list_item', 'content': "Error-based injection exploiting GTID_SUBSET function: user2del=111' AND GTID_SUBSET(CONCAT(0x7170707171,(SELECT (ELT(2680=2680,1))),0x716a767a71),2680)--"}, {'type': 'list_item', 'content': "Time-based blind injection using SLEEP function: user2del=111' AND (SELECT 2957 FROM (SELECT(SLEEP(5)))rWXw)--"}, {'type': 'paragraph', 'content': 'Testing can be automated using tools like sqlmap targeting the vulnerable endpoint with the appropriate parameters.'}] [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection.

Strict input validation and filtering should be applied to ensure inputs conform to expected formats, such as numeric patterns for user IDs.

Minimize database user permissions by avoiding the use of high-privilege accounts for routine operations.

Conduct regular security audits to detect and address vulnerabilities promptly.


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