CVE-2025-12326VulnerabilityPublished 27 Oct 2025

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

Affects shawon100 RUET OJSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 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.

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.

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.

Summary

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.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

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

Technical details

References

Community reviews

Related threats