CVE-2025-9761
BaseFortify
Publication date: 2025-09-01
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_feeds_product_inventory_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-9761 is a critical SQL injection vulnerability in the Online Feeds Product Inventory System version 1.0, specifically in the /feeds/index.php file. The vulnerability occurs because the 'username' 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 attack can be performed remotely without authentication and is considered easy to exploit. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data, data modification, deletion, and potentially full system compromise or service disruption. Attackers can remotely execute SQL injection attacks without authentication, which may result in loss of data confidentiality, integrity, and availability. This can severely impact the security and operation of the affected system. [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 'username' parameter in the /feeds/index.php file for SQL injection flaws. You can use tools like sqlmap to automate detection and enumeration. Example payloads for manual testing include boolean-based blind SQL injection (e.g., username=-5931' OR 4471=4471 #), error-based SQL injection (e.g., username=admin' AND GTID_SUBSET(CONCAT(0x7162626b71,(SELECT (ELT(8432=8432,1))),0x7178717a71),8432)-- aCRi), and time-based blind SQL injection (e.g., username=admin' AND (SELECT 7130 FROM (SELECT(SLEEP(5)))YzLo)-- JuOr). Additionally, you can search for vulnerable targets using Google dorking with queries like inurl:feeds/index.php. [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 all user inputs, and minimizing database user privileges by avoiding high-privilege accounts such as 'root' or 'admin' for routine operations. Regular security audits should be conducted to detect and remediate vulnerabilities promptly. Since no known patches or countermeasures are reported, replacing the affected product with an alternative solution is also suggested. [2, 3, 1]