CVE-2026-3133
SQL Injection in itsourcecode DMS Login Allows Remote Exploitation
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
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-3133 is a SQL injection vulnerability found in the itsourcecode Document Management System version 1.0, specifically in the /loging.php file within the Login component.'}, {'type': 'paragraph', 'content': "The vulnerability occurs because the application does not properly sanitize or validate the 'username' parameter before using it in SQL queries during the login process."}, {'type': 'paragraph', 'content': "This flaw allows an attacker to inject malicious SQL code via the 'username' field without needing valid credentials, enabling unauthorized manipulation of the database."}] [1, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to leak sensitive data, tamper with data, gain full system control, and potentially disrupt services.
Since the attack can be performed remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the affected system.
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 /loging.php endpoint for SQL injection via the 'username' parameter in POST requests."}, {'type': 'paragraph', 'content': 'One can use tools like sqlmap to automate detection. An example command to test the vulnerability is:'}, {'type': 'list_item', 'content': 'python sqlmap.py --random-agent --batch -u "http://<target-ip-or-domain>/loging.php" --data "username=admin&password=admin" --dbms=mysql --current-db'}, {'type': 'paragraph', 'content': "Additionally, manual testing can be done using proof-of-concept payloads such as boolean-based blind SQL injection: username=admin' AND 5174=5174 AND 'OnWO'='OnWO&password=admin or time-based blind SQL injection: username=admin' AND (SELECT 8326 FROM (SELECT(SLEEP(5)))jdTB) AND 'rPEF'='rPEF&password=admin"}, {'type': 'paragraph', 'content': 'Vulnerable targets can also be identified using Google dorking with queries like: inurl:loging.php'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Use prepared statements and parameter binding to separate SQL code from user input, preventing SQL injection.
- Implement strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding high-privilege accounts for routine operations.
- Conduct regular security audits to detect and address vulnerabilities promptly.
If possible, consider replacing the affected product with an alternative solution as no known countermeasures or mitigations have been documented.