CVE-2025-12252
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-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-12252 is a SQL injection vulnerability in the Online Event Judging System version 1.0, specifically in the file /ajax/action.php. It occurs because the application improperly handles the 'content' argument, allowing an attacker to inject malicious SQL code remotely without authentication. This happens due to insufficient sanitization or validation of user input, enabling attackers to manipulate SQL queries directly. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data modification or deletion, full system compromise, and potential service disruption. Attackers can exploit it remotely to manipulate SQL queries, threatening 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 /ajax/action.php endpoint for SQL injection via the 'content' parameter. A proof-of-concept payload for a time-based blind SQL injection is: content=111' AND (SELECT 5872 FROM (SELECT(SLEEP(5)))rKkJ) AND 'LZJW'='LZJW. You can use tools like curl or sqlmap to test this. For example, using curl: curl -X POST -d "content=111' AND (SELECT 5872 FROM (SELECT(SLEEP(5)))rKkJ) AND 'LZJW'='LZJW" http://target/ajax/action.php. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:ajax/action.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replace the affected software with an alternative product as no known countermeasures are documented. 2) If replacement is not immediately possible, implement prepared statements with parameter binding to prevent SQL injection. 3) Apply strict input validation and filtering on the 'content' parameter to ensure it conforms to expected formats. 4) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 5) Conduct regular security audits to detect and fix vulnerabilities promptly. [2, 3]