CVE-2025-6835
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-6835 is a critical SQL injection vulnerability in the code-projects Library System version 1.0, specifically in the file /student-issue-book.php. The vulnerability occurs because the 'reg' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely, which can manipulate the database in unauthorized ways. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to view, modify, or delete sensitive information. It can also enable attackers to take control of the system, disrupt services, and compromise data integrity and confidentiality. [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 checking for the presence of the vulnerable file "/student-issue-book.php" on your system or web server. Additionally, you can use Google dorking with the query "inurl:student-issue-book.php" to identify potentially vulnerable targets. To detect exploitation attempts on your network, monitor HTTP requests for suspicious or malicious input in the 'reg' parameter that may indicate SQL injection attempts. Specific commands are not provided, but monitoring web server logs for unusual queries targeting the 'reg' parameter in "/student-issue-book.php" is recommended. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements (parameterized queries) to ensure user inputs in the 'reg' parameter are treated as data and not executable SQL code. 2) Applying strict input validation and filtering on the 'reg' parameter to ensure inputs conform to expected formats. 3) Limiting database user permissions to the minimum necessary privileges, avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits of code and systems to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected component with an alternative product as no known countermeasures are documented. [2, 3]