CVE-2026-9528: itsourcecode Electronic Judging System delete_judge.php sql injection
A vulnerability was identified in itsourcecode Electronic Judging System 1.0. Impacted is an unknown function of the file /admin/delete_judge.php. Such manipulation of the argument judge_id leads to sql injection. The attack can be executed remotely. The exploit is publicly available and might be used.
CVE-2026-9528 is a SQL injection in itsourcecode Electronic Judging System 1.0. A remote attacker may manipulate judge_id in /admin/delete_judge.php to affect the database. Public proof-of-concept material is reported, but the bundle does not show confirmed active exploitation or an official patch.
Executive priority
Prioritize within the current vulnerability cycle for any reachable deployment. Escalate to urgent if the system stores sensitive student, judge, credential, or scoring data, or if the admin path is internet accessible.
Technical view
The issue is reported as CWE-89/CWE-74 in /admin/delete_judge.php, where judge_id is not safely handled before SQL use. CVSS v2 is 7.5 with network access, low complexity, and no authentication. Confidentiality, integrity, and availability impacts are partial.
Likely exposure
Exposure is limited to organizations running itsourcecode Electronic Judging System 1.0, especially deployments reachable from the internet or broadly reachable internally. The affected route is under /admin, but the supplied CVSS vector says authentication is not required.
Exploitation context
The source bundle says exploit code is publicly available and might be used. CISA KEV status is false, and no cited source confirms active exploitation. Treat this as elevated risk because SQL injection can expose or alter application data.
Researcher notes
Evidence is recent and source-limited. The affected function is unnamed, remediation is not specified, and vendor confirmation is not shown in the bundle. Avoid assuming broader versions are affected beyond Electronic Judging System 1.0.
Mitigation direction
Check vendor guidance and advisories for an official fix or replacement package.
Restrict access to the affected application and admin paths to trusted networks.
Apply compensating controls such as WAF rules for suspicious judge_id requests.
Review code for unsafe SQL handling and use parameterized queries if maintaining the application.
Back up the database before remediation and confirm backups can restore cleanly.
Validation and detection
Inventory systems for itsourcecode Electronic Judging System version 1.0.
Confirm whether /admin/delete_judge.php is present and reachable.
Review web and application logs for abnormal judge_id values or database errors.
Check database integrity for unexpected judge deletion or modification activity.
Validate fixes in a controlled environment without using public exploit instructions.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-74 · source CWE mapping
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.