CVE-2025-12328VulnerabilityPublished 27 Oct 2025

CVE-2025-12328: shawon100 RUET OJ · SQL Injection

Affects shawon100 RUET OJSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

European organizations should immediately implement strict input validation and sanitization on all parameters, especially the 'Name' argument in /contestproblem.php, to prevent SQL injection. Employ parameterized queries or prepared statements if source code access is available. Deploy Web Application Firewalls (WAFs) configured to detect and block SQL injection patterns targeting the RUET OJ platform. Monitor database logs for unusual queries or error messages indicative of injection attempts. Isolate the RUET OJ environment from critical internal networks to limit lateral movement in case of compromise. Regularly back up contest and user data to enable recovery from potential data corruption. Engage with the community or vendor forums to track any unofficial patches or updates. Consider alternative contest management platforms if timely patches are not forthcoming. Finally, conduct security audits and penetration tests focused on injection vulnerabilities within the platform.

Description

A vulnerability was identified in shawon100 RUET OJ up to 18fa45b0a669fa1098a0b8fc629cf6856369d9a5. Impacted is an unknown function of the file /contestproblem.php. Such manipulation of the argument Name leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, particularly universities, coding bootcamps, and competitive programming platforms using RUET OJ, this vulnerability could lead to unauthorized access to sensitive contest problems, user credentials, or scoring data. The integrity of contest results could be compromised, undermining trust in the platform. Confidentiality breaches could expose participant information or proprietary problem sets. Availability might be affected if attackers execute destructive SQL commands or cause database corruption. Since the exploit requires no authentication or user interaction, attackers can launch automated attacks at scale, increasing risk. The absence of vendor patches elevates the threat level, as organizations must rely on their own mitigations. This vulnerability could also be leveraged as a foothold for further attacks within academic networks, potentially impacting broader IT infrastructure.

Summary

CVE-2025-12328 identifies a SQL injection vulnerability in the shawon100 RUET OJ platform, a system used for online programming contests and problem management. The vulnerability resides in an unspecified function within the /contestproblem.php file, where the 'Name' parameter is improperly sanitized, allowing attackers to inject malicious SQL code. This injection can be performed remotely without authentication or user interaction, increasing the attack surface. The rolling release development model of RUET OJ means that there are no fixed version numbers for affected or patched releases, complicating vulnerability management. The vendor was notified but has not responded or issued a patch, and although exploits exist publicly, there are no confirmed reports of exploitation in the wild. The CVSS v4.0 score of 5.3 (medium severity) reflects the vulnerability’s moderate impact and ease of exploitation without privileges or user interaction. Successful exploitation could allow attackers to read, modify, or delete database contents, potentially compromising sensitive contest data, user information, or system integrity. The lack of segmentation or scope change in the CVSS vector suggests the impact is limited to the affected component. Given the nature of the platform, the vulnerability poses risks to educational institutions and organizations relying on RUET OJ for contest management or training.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Nov 2025, 03:19 UTC

Technical details

References

Community reviews

Related threats