CVE-2025-9692
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 |
|---|---|---|
| campcodes | online_shopping_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-9692 is a critical SQL injection vulnerability in the Campcodes Online Shopping System version 1.0, specifically in the /product.php file. It occurs because the 'p' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially leading to data leakage, modification, deletion, or full system compromise. The vulnerability can be exploited remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized retrieval, modification, or deletion of sensitive data stored in the database. Attackers can gain unauthorized access to confidential information, disrupt system availability, and potentially take full control of the affected system. This poses significant risks to data integrity, confidentiality, 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 /product.php endpoint with SQL injection payloads targeting the 'p' parameter. Example commands include using sqlmap to automate detection, e.g., `sqlmap -u "http://target/product.php?p=1" --batch`. Manual testing can involve sending HTTP requests with payloads such as `p=1 AND 5936=5936` (Boolean-based blind injection), error-based payloads like `p=1 AND (SELECT 5051 FROM(SELECT COUNT(*),CONCAT(0x716b7a6a71,(SELECT (ELT(5051=5051,1))),0x717a627871,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)`, or UNION-based injections like `p=1 UNION ALL SELECT NULL,NULL,NULL,NULL,CONCAT(0x716b7a6a71,0x4a416f4d6e615a5a626a4a757151475874786e7453427846686f526a45556f697a53507544515159,0x717a627871),NULL,NULL,NULL-- -`. Additionally, Google dorking with queries such as `inurl:product.php` can help identify vulnerable targets. [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 'p' parameter to ensure it conforms to expected formats, and minimizing database user permissions by avoiding the use of high-privilege accounts (such as root or admin) for the application's database connections. Regular security audits should be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected product with an alternative solution is recommended as no known countermeasures are documented. [2, 3]