CVE-2026-3153
SQL Injection in itsourcecode DMS /register.php Allows Remote Exploit
Publication date: 2026-02-25
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| admerc | document_management_system | 1.0 |
Helpful Resources
Exploitability
| 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
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, data tampering, and potentially full system control by attackers.
It can also lead to service disruption and compromise the confidentiality, integrity, and availability of the affected system.
Since exploitation requires no authentication and can be performed remotely, the risk and accessibility for attackers are high.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-3153 is a critical SQL injection vulnerability found in the itsourcecode Document Management System version 1.0, specifically in the /register.php file.'}, {'type': 'paragraph', 'content': "The vulnerability occurs because the application does not properly sanitize or validate the 'username' parameter received during user registration. This allows an attacker to inject malicious SQL code remotely without needing to authenticate."}, {'type': 'paragraph', 'content': 'Exploitation techniques include Boolean-based blind SQL injection, error-based SQL injection, and time-based blind SQL injection, enabling attackers to manipulate SQL queries executed by the system.'}] [1, 2, 3]
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 'username' parameter in POST requests to the /register.php file for SQL injection weaknesses."}, {'type': 'paragraph', 'content': 'One suggested method is to use the sqlmap tool to automate detection of SQL injection. An example command is:'}, {'type': 'list_item', 'content': 'python sqlmap.py --random-agent --batch -u "http://<target-ip>:<port>/register.php" --data "username=admin&password=admin" --dbms=mysql --current-db'}, {'type': 'paragraph', 'content': "Additionally, manual testing can be performed using payloads such as Boolean-based blind SQL injection (e.g., username=admin' AND 1767=1767 AND 'UQpP'='UQpP), error-based SQL injection, or time-based blind SQL injection payloads to observe the application's response."}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Implement prepared statements and parameter binding to separate SQL code from user input, preventing injection.
- Apply strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding the use of high-privilege accounts for routine operations.
- Conduct regular security audits to detect and fix vulnerabilities promptly.
If possible, consider replacing the affected software with an alternative product as no known mitigations or countermeasures have been reported.