CVE-2025-10104
BaseFortify
Publication date: 2025-09-08
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 |
|---|---|---|
| carmelo | online_event_judging_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-10104 is a critical SQL injection vulnerability in version 1.0 of the code-projects Online Event Judging System. It exists in the /review_search.php file due to improper handling and insufficient validation of the 'txtsearch' parameter. This flaw allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized access to the database. Attackers can retrieve, modify, or delete sensitive data, compromising the system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized data retrieval, modification, or deletion, resulting in compromised sensitive information and data integrity. It can also cause full system compromise and potential service disruption. Since the attack can be performed remotely without authentication and is easy to execute, it poses a severe risk to 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 'txtsearch' parameter in the /review_search.php file for SQL injection flaws. You can use tools like sqlmap to automate detection. Example payloads for manual testing include boolean-based blind, error-based, stacked queries, time-based blind, and UNION queries, such as: - Boolean-based blind: txtsearch=1' AND 5235=5235 # - Error-based: txtsearch=1' AND (SELECT 6199 FROM(SELECT COUNT(*),CONCAT(0x7170626271,(SELECT (ELT(6199=6199,1))),0x71717a7071,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- mUxF - Stacked queries: txtsearch=1';SELECT SLEEP(5) # - Time-based blind: txtsearch=1' AND (SELECT 3017 FROM (SELECT(SLEEP(5)))tWpp)-- BxNK - UNION query: txtsearch=1' UNION ALL SELECT NULL,CONCAT(0x7170626271,0x474362785776426f414a53656a795a68414f4563716e65434357754c634a476246466159484255,0x71717a7071),NULL,NULL,NULL,NULL,NULL,NULL # Using sqlmap command example: sqlmap -u "http://target/review_search.php" --data="txtsearch=1" --risk=3 --level=5 --batch [3, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Replace the affected software with an alternative product if possible. - Implement prepared statements with parameter binding to separate SQL code from user input. - Apply strict input validation and filtering on the 'txtsearch' parameter to ensure inputs conform to expected formats. - Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. - Conduct regular security audits to detect and address vulnerabilities promptly. Since no known patches or countermeasures are documented, these steps are critical to reduce risk. [3, 2, 1]