CVE-2025-6836
BaseFortify
Publication date: 2025-06-29
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 |
|---|---|---|
| code-projects | library_system | 1.0 |
Helpful Resources
Exploitability
| 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?
CVE-2025-6836 is a critical SQL injection vulnerability in the code-projects Library System version 1.0, specifically in the /profile.php file. It occurs because the 'phone' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL commands. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, leakage of sensitive information, data tampering, deletion of data, and potentially full system compromise or service disruption. Since the exploit requires no authentication and can be launched remotely, attackers can easily exploit this flaw to harm system confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'phone' parameter in the /profile.php file for SQL injection. Tools like sqlmap can be used to automate detection and confirm the injection point. A proof-of-concept payload to test time-based blind SQL injection is: phone=01956659918' AND (SELECT 8978 FROM (SELECT(SLEEP(5)))TICw) AND 'msOJ'='msOJ, which causes a delay in the database response if vulnerable. Additionally, attackers may use Google dorking with queries like inurl:profile.php to identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. Since no known countermeasures or patches are available, replacing the affected component with an alternative product is also suggested. [2, 3]