CVE-2025-12255
BaseFortify
Publication date: 2025-10-27
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-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
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, alteration or deletion of data, full system compromise, and disruption of service availability. Attackers can exploit this remotely without authentication, potentially taking full control over the affected system. [1, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'fullname' parameter in the /add_contestant.php file for SQL injection. Automated tools like sqlmap can be used to confirm the presence of the vulnerability by injecting payloads and observing the response, such as time delays caused by the SLEEP function in the database. Additionally, attackers may locate vulnerable targets using Google dorking with the query "inurl:add_contestant.php". Example command using sqlmap: sqlmap -u "http://targetsite/add_contestant.php" --data="fullname=test" --technique=BEUSTQ --dbms=mysql --time-sec=5 [1, 4]
Can you explain this vulnerability to me?
CVE-2025-12255 is a critical SQL injection vulnerability in version 1.0 of the Online Event Judging System, specifically in the add_contestant.php file. The vulnerability occurs because the application directly uses user input from the 'fullname' parameter in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, potentially manipulating the database in unauthorized ways. [1, 2, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering on the 'fullname' parameter to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replace the affected software with an alternative product. [1, 4]