CVE-2025-12262VulnerabilityPublished 27 Oct 2025

CVE-2025-12262: code-projects Online Event Judging System · SQL Injection

Affects code-projects Online Event Judging SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% 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-25.

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

Affected software

Product	Affected	Fixed in
code-projects Online Event Judging System	Affected =1.0	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should first check for any official patches or updates from the vendor and apply them promptly once available. In the absence of patches, implement strict input validation on the crit_id parameter to ensure only expected numeric or predefined values are accepted. Employ parameterized queries or prepared statements in the application code to prevent SQL injection. Deploy web application firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting the /edit_criteria.php endpoint. Conduct thorough code reviews and security testing of the application to identify and remediate similar injection points. Limit database user privileges to the minimum necessary to reduce the impact of a successful injection. Monitor logs for suspicious activity related to crit_id parameter manipulation. Finally, consider isolating the judging system network segment to reduce exposure to external threats.

Description

A vulnerability was determined in code-projects Online Event Judging System 1.0. This impacts an unknown function of the file /edit_criteria.php. Executing manipulation of the argument crit_id can lead to sql injection. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized.

Impact

For European organizations, the impact of this vulnerability could be significant if they rely on the code-projects Online Event Judging System for managing events, competitions, or evaluations. Exploitation could lead to unauthorized access to sensitive judging criteria or participant data, potentially compromising confidentiality. Integrity could be affected by unauthorized modification of judging parameters, which may undermine the fairness and trustworthiness of events. Availability impacts, while rated low, could still disrupt event operations if attackers manipulate the database or cause errors. Organizations in sectors such as education, professional associations, or event management that use this software may face reputational damage and operational disruptions. Given the remote exploitability without authentication, attackers could target these systems from anywhere, increasing the threat landscape. The medium severity rating suggests moderate urgency but should not be ignored, especially in environments where data integrity and confidentiality are critical.

Summary

CVE-2025-12262 is a SQL injection vulnerability identified in the code-projects Online Event Judging System version 1.0. The vulnerability exists in the /edit_criteria.php file, where the crit_id parameter is improperly sanitized, allowing attackers to inject malicious SQL code. This injection flaw can be exploited remotely without requiring authentication or user interaction, making it accessible to unauthenticated attackers over the network. The vulnerability impacts the confidentiality, integrity, and availability of the underlying database, although the CVSS 4.0 vector indicates low impact on each (VC:L, VI:L, VA:L). The CVSS score of 5.3 classifies it as medium severity. The flaw could allow attackers to extract sensitive data, modify event judging criteria, or disrupt the system's normal operation. No known exploits are currently active in the wild, but public disclosure increases the risk of exploitation attempts. The lack of available patches means organizations must rely on mitigating controls such as input validation or web application firewalls until an official fix is released. The vulnerability affects only version 1.0 of the product, so upgrading to a patched version when available is critical.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 11:26 UTC

Technical details

References

Community reviews

Related threats