CVE-2025-9700
BaseFortify
Publication date: 2025-08-30
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 |
|---|---|---|
| janobe | online_book_store | 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-9700 is a critical SQL injection vulnerability in SourceCodester Online Book Store version 1.0, specifically in the /publisher_list.php file. The vulnerability occurs because the 'pubid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of database queries, such as retrieving, modifying, or deleting data without permission. The attack can be performed remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive data, data modification, or deletion, compromising the confidentiality, integrity, and availability of the system. Attackers can exploit it remotely without authentication, potentially causing data breaches, service disruptions, or even full system compromise, severely affecting system security and business continuity. [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 'pubid' parameter in the /publisher_list.php file for SQL injection. A common approach is to use automated tools like sqlmap to test for SQL injection by targeting the URL parameter. For example, using sqlmap with a command like: sqlmap -u "http://yourserver/publisher_list.php?pubid=1" --batch --dbs can help identify if the parameter is vulnerable. Additionally, attackers may be identified by monitoring for unusual requests to /publisher_list.php with suspicious or malformed 'pubid' values. Google dorking with queries such as inurl:publisher_list.php can also help identify vulnerable instances externally. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'pubid' parameter, and limiting database user permissions to the minimum necessary to reduce impact. Avoid using high-privilege accounts like 'root' or 'admin' for routine database operations. Conduct regular security audits to detect and fix vulnerabilities promptly. If possible, consider replacing the affected software with a secure alternative, as no known countermeasures are documented. [2, 3]