Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12326: SQL Injection in shawon100 RUET OJ

0
Medium
VulnerabilityCVE-2025-12326cvecve-2025-12326
Published: Mon Oct 27 2025 (10/27/2025, 21:02:05 UTC)
Source: CVE Database V5
Vendor/Project: shawon100
Product: RUET OJ

Description

A vulnerability was found in shawon100 RUET OJ up to 18fa45b0a669fa1098a0b8fc629cf6856369d9a5. This vulnerability affects unknown code of the file /process.php of the component POST Request Handler. The manipulation of the argument un results in sql injection. The attack can be launched remotely. The exploit has been made public and could be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 11/04/2025, 03:22:19 UTC

Technical Analysis

CVE-2025-12326 identifies a SQL injection vulnerability in the shawon100 RUET OJ online judge platform, affecting the /process.php file's POST request handler. The vulnerability arises from improper sanitization of the 'un' parameter, which attackers can manipulate to inject malicious SQL statements. This injection flaw enables remote, unauthenticated attackers to execute arbitrary SQL commands, potentially leading to unauthorized data access, data modification, or disruption of service. The vulnerability does not require user interaction or privileges, increasing its exploitability. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) reflects network attack vector, low attack complexity, no privileges or user interaction needed, and partial impacts on confidentiality, integrity, and availability. The vendor has not provided patches or versioning information, complicating mitigation efforts. Although no active exploitation has been reported, public exploit code availability elevates the risk of future attacks. The lack of versioning and vendor response suggests potential challenges in identifying affected deployments and applying fixes. This vulnerability is particularly concerning for organizations relying on RUET OJ for programming competitions or educational assessments, as it could compromise sensitive user data or disrupt platform operations.

Potential Impact

For European organizations, especially academic institutions and competitive programming platforms using RUET OJ, this vulnerability poses a risk of unauthorized data disclosure, data tampering, and service disruption. Attackers exploiting this flaw could access sensitive user information such as credentials, personal data, or contest results, undermining privacy and trust. Integrity violations could allow manipulation of contest submissions or results, affecting fairness and reputation. Availability impacts could disrupt platform accessibility, impeding educational activities. Given the remote, unauthenticated exploitability, attackers can launch attacks at scale, potentially targeting multiple institutions. The absence of vendor patches increases the window of exposure. Furthermore, regulatory frameworks like GDPR impose strict data protection requirements, and breaches resulting from this vulnerability could lead to legal and financial consequences for European entities. The medium severity rating indicates a significant but not critical threat, yet the ease of exploitation and potential impact on educational services warrant urgent attention.

Mitigation Recommendations

European organizations should implement immediate mitigations including: 1) Applying input validation and sanitization on the 'un' parameter and all user inputs to prevent SQL injection. 2) Refactoring the codebase to use parameterized queries or prepared statements instead of dynamic SQL construction. 3) Deploying web application firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting /process.php. 4) Monitoring database logs and application logs for anomalous queries or access patterns indicative of exploitation attempts. 5) Isolating the RUET OJ platform within segmented network zones to limit lateral movement if compromised. 6) Conducting security audits and penetration testing focused on injection vulnerabilities. 7) Engaging with the vendor or community to encourage patch development or sharing of secure versions. 8) Educating developers and administrators about secure coding practices and the risks of unsanitized inputs. 9) Considering temporary disabling or restricting access to vulnerable components until a patch is available. These measures go beyond generic advice by focusing on immediate code-level fixes, network defenses, and operational monitoring tailored to this specific vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-10-27T10:21:11.561Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68ffdf31ba6dffc5e20e9771

Added to database: 10/27/2025, 9:08:01 PM

Last enriched: 11/4/2025, 3:22:19 AM

Last updated: 12/10/2025, 10:55:59 PM

Views: 56

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats