CVE-2025-10841
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-10841 is a critical SQL injection vulnerability in version 1.0 of the code-projects Online Bidding System, specifically in the /administrator/weweee.php file. It occurs because the 'ID' argument is not properly validated or neutralized, allowing attackers to inject malicious SQL commands remotely without authentication. This flaw enables unauthorized modification of SQL queries, potentially compromising the system's database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute arbitrary SQL commands on your database without authentication. This can lead to unauthorized access, modification, or deletion of data, compromising the confidentiality, integrity, and availability of your system. The exploit is publicly available and easy to execute, increasing the risk of attack. [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/weweee.php and testing the 'ID' parameter for SQL injection flaws. One method to identify vulnerable targets is using Google dorking with the query: inurl:administrator/weweee.php. For active testing, you can use tools like sqlmap to test the 'ID' parameter for SQL injection, for example: sqlmap -u "http://target/administrator/weweee.php?id=1" --batch. Monitoring network traffic for suspicious SQL injection patterns targeting this URL can also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps include replacing the affected component with an alternative product, as no known countermeasures or mitigations have been documented. Additionally, restricting access to the /administrator/weweee.php file, applying web application firewalls (WAF) to block SQL injection attempts, and monitoring for exploitation attempts are recommended until a secure fix or patch is available. [1, 2]