CVE-2025-12329VulnerabilityPublished 27 Oct 2025

CVE-2025-12329: 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 20% 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

1. Immediately implement strict input validation and sanitization on all parameters, especially the 'ID' parameter in /details.php, using parameterized queries or prepared statements to prevent SQL injection. 2. Deploy a Web Application Firewall (WAF) with rules targeting SQL injection patterns to detect and block malicious requests. 3. Monitor database logs and web server logs for unusual query patterns or repeated failed attempts to exploit the vulnerability. 4. If possible, isolate the RUET OJ instance from critical internal networks to limit potential lateral movement. 5. Conduct a thorough code review of the application to identify and remediate other potential injection points. 6. Engage with the community or maintainers to track any forthcoming patches or updates despite the vendor's current non-responsiveness. 7. Consider migrating to alternative, actively maintained online judging platforms with robust security practices if remediation is not feasible. 8. Educate administrators and developers on secure coding practices and the risks of SQL injection. 9. Regularly back up databases and ensure backups are secure and tested for restoration to mitigate data loss from potential attacks. 10. Implement network-level restrictions to limit access to the application to trusted users or IP ranges where possible.

Description

A security flaw has been discovered in shawon100 RUET OJ up to 18fa45b0a669fa1098a0b8fc629cf6856369d9a5. The affected element is an unknown function of the file /details.php. Performing manipulation of the argument ID results in sql injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact of this SQL injection vulnerability could be significant, especially for universities, coding bootcamps, or competitive programming platforms using RUET OJ or similar open-source judging systems. Exploitation could lead to unauthorized access to sensitive user data, including personal information and contest submissions, undermining privacy and data protection compliance under GDPR. Integrity of contest results or educational records could be compromised, affecting trust and fairness. Availability could also be impacted if attackers use SQL injection to disrupt database operations or cause denial of service. Given the public availability of exploit code and lack of vendor patching, the risk of attacks targeting European academic institutions or tech companies using this platform increases. The rolling release nature complicates patch management, potentially delaying remediation. Organizations may face reputational damage, regulatory penalties, and operational disruption if the vulnerability is exploited.

Summary

CVE-2025-12329 identifies a SQL injection vulnerability in the shawon100 RUET OJ system, a platform likely used for online judging in programming contests or educational purposes. The vulnerability resides in an unspecified function within the /details.php file, where the 'ID' parameter is improperly sanitized, allowing attackers to inject malicious SQL statements. This injection can be performed remotely without authentication or user interaction, making exploitation straightforward. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the attack vector is network-based with low attack complexity and no privileges or user interaction required, but with limited impact on confidentiality, integrity, and availability. Publicly available exploit code increases the risk of exploitation, potentially leading to unauthorized data access, data manipulation, or disruption of service. The vulnerability affects all deployments running the specified commit or earlier, with no clear indication of fixed versions. The lack of vendor response and patch availability necessitates proactive defensive measures by users. The vulnerability is particularly concerning for organizations relying on RUET OJ for educational or competitive programming environments, where sensitive user data or contest integrity could be compromised.

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