CVE-2025-10842
BaseFortify
Publication date: 2025-09-23
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 |
|---|---|---|
| fabian | online_bidding_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10842 is a SQL injection vulnerability in version 1.0 of the code-projects Online Bidding System, specifically in the /administrator/wew.php file. The vulnerability occurs because the application improperly handles the 'id' parameter in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely, manipulating database queries to retrieve, modify, or delete data without authorization. [1, 2]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing remote attackers to execute unauthorized SQL commands on your database. This can lead to unauthorized data access, data modification, or deletion, compromising the confidentiality, integrity, and availability of your system. Since the exploit is publicly available and easy to execute without authentication, it poses a high risk to affected systems. [1, 2]
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 /administrator/wew.php and testing the 'id' parameter for SQL injection. One detection method is to use Google dorking with the query "inurl:administrator/wew.php" to identify potentially vulnerable targets. For direct testing, you can use tools like curl or sqlmap to send crafted requests to the 'id' parameter and observe if SQL injection is possible. Example command with curl: curl "http://target/administrator/wew.php?id=1' OR '1'='1". Alternatively, sqlmap can be used to automate detection: sqlmap -u "http://target/administrator/wew.php?id=1" --batch. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the vulnerable /administrator/wew.php file, especially from untrusted networks. Since no known mitigations or patches are documented, it is recommended to replace the affected component with an alternative product or apply input validation and parameterized queries to the 'id' parameter to prevent SQL injection. Additionally, monitor for exploit attempts and consider implementing web application firewall (WAF) rules to block malicious input targeting this vulnerability. [2, 1]