CVE-2025-12327VulnerabilityPublished 27 Oct 2025

CVE-2025-12327: 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, 08:30 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 26 Oct 2026.

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

Since no official patches are available, European organizations should implement immediate compensating controls. First, apply strict input validation and sanitization on the 'ID' parameter in /description.php, ensuring only expected numeric or alphanumeric values are accepted. Employ parameterized queries or prepared statements in the database access layer to prevent SQL injection. Conduct thorough code reviews and static analysis to identify similar injection points. Monitor database logs and application logs for unusual query patterns or error messages indicative of injection attempts. Restrict database user privileges to the minimum necessary to limit potential damage from injection exploits. If feasible, deploy web application firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting this endpoint. Educate development and security teams about the vulnerability and encourage rapid incident response readiness. Finally, maintain close monitoring of vendor communications for any future patches or updates and plan for timely application once available.

Description

A vulnerability was determined in shawon100 RUET OJ up to 18fa45b0a669fa1098a0b8fc629cf6856369d9a5. This issue affects some unknown processing of the file /description.php. This manipulation of the argument ID causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. 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 shawon100 RUET OJ, this vulnerability poses significant risks. Exploitation could lead to unauthorized disclosure of sensitive user data, including participant submissions, personal information, or competition results, undermining privacy and trust. Data integrity could be compromised by unauthorized modification or deletion of database records, potentially affecting competition fairness or record accuracy. Availability impacts may arise if attackers execute commands that disrupt database operations or cause service outages, impacting ongoing assessments or contests. The medium CVSS score reflects moderate but tangible risks, especially given the unauthenticated remote exploit vector. European organizations with limited security resources or delayed patching processes are particularly vulnerable. Additionally, the absence of vendor patches and public exploit code increases the urgency for internal mitigations. The reputational damage and potential regulatory consequences under GDPR for data breaches further elevate the impact for affected European entities.

Summary

CVE-2025-12327 identifies an SQL injection vulnerability in the shawon100 RUET OJ online judge platform, specifically in the handling of the 'ID' parameter within the /description.php endpoint. This vulnerability arises from improper sanitization or validation of user-supplied input, allowing attackers to inject arbitrary SQL commands into backend database queries. The injection can be performed remotely without authentication or user interaction, indicating a network-exploitable flaw with low complexity but requiring low privileges. The vulnerability affects versions up to the commit hash 18fa45b0a669fa1098a0b8fc629cf6856369d9a5, but due to the product's rolling release model, exact versioning is ambiguous. The vendor was contacted but did not respond, and no official patches or fixes have been released. The CVSS 4.0 base score is 5.3 (medium), reflecting moderate impact on confidentiality, integrity, and availability with partial scope impact. Exploitation could allow attackers to extract sensitive data, modify database contents, or disrupt service availability. Although no known exploits are currently active in the wild, the public disclosure of the vulnerability increases the likelihood of future exploitation attempts. The lack of vendor response and patch availability necessitates proactive mitigation by users of the platform. Given the nature of the platform as an online judge system, typically used in academic or competitive programming environments, the threat primarily targets educational institutions or organizations relying on this software for coding competitions or assessments.

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