CVE-2025-11585
BaseFortify
Publication date: 2025-10-10
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 |
|---|---|---|
| fabian | project_monitoring_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?
CVE-2025-11585 is a critical SQL injection vulnerability in version 1.0 of the code-projects Project Monitoring System, specifically in the /useredit.php file. The vulnerability occurs because the 'uid' parameter is improperly handled and directly incorporated into SQL queries without proper sanitization or validation. This allows remote attackers to inject malicious SQL code without authentication, leading to unauthorized database access, data leakage, data tampering, and potential full system control. [1, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability allows attackers to gain direct and unrestricted access to the backend database. They can exfiltrate sensitive data such as user login credentials, personally identifiable information (PII), and proprietary project data. Attackers can also manipulate or destroy critical data, disrupt business operations, compromise data integrity, and potentially take full control of the affected system. The attack can be executed remotely without any prior authentication, making it highly dangerous. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for the presence of the vulnerable endpoint "/useredit.php" on your system or network, for example using Google dorking with the query "inurl:useredit.php" to identify exposed targets. Additionally, testing can be performed by sending crafted POST requests to "/useredit.php" with manipulated "uid" parameters to check for SQL injection behavior. Tools like sqlmap can be used to automate detection and confirm exploitability against the backend database. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known mitigations are documented. If replacement is not immediately possible, implement prepared statements with parameter binding to separate SQL code from user input, enforce rigorous input validation and filtering on the "uid" parameter, and minimize database user permissions to reduce potential impact. These measures help prevent SQL injection and limit damage if exploited. [1, 3]