Analyst readout for executives and security teams
Plain-English summary
Electronic Judging System 1.0 has a SQL injection issue in an admin PHP page. If deployed, an attacker may be able to manipulate database queries remotely through the judge_id parameter, risking confidentiality, integrity, and availability of stored data.
Executive priority
Treat as high priority if this product is deployed. Public exploit disclosure increases urgency, but current evidence does not prove active exploitation. Focus first on identifying deployments and removing public exposure.
Technical view
CVE-2026-9525 affects itsourcecode Electronic Judging System 1.0 in /admin/edit_judge.php. The judge_id argument is reported as SQL injectable. The record maps to CWE-89 and CWE-74 with CVSS 2.0 score 7.5, network attack vector, low complexity, and no authentication required.
Likely exposure
Exposure appears limited to organizations running itsourcecode Electronic Judging System 1.0, especially where the admin route is reachable from untrusted networks. The sources do not quantify install base or confirm managed/cloud deployments.
Exploitation context
The exploit is publicly disclosed and the VulDB description says it may be used. The source bundle does not show CISA KEV listing or cited evidence of active exploitation in the wild.
Researcher notes
The record does not name a patched version, specific vulnerable code block, or vendor advisory. Validation should stay defensive: confirm product/version, route exposure, parameter handling, and whether compensating controls prevent untrusted access.
Mitigation direction
- Check vendor guidance for an official fix or replacement release.
- Restrict access to /admin/ paths to trusted networks or VPN users.
- Prioritize migration if version 1.0 cannot be patched.
- Review database permissions used by the application for least privilege.
- Monitor web and database logs for suspicious judge_id activity.
Validation and detection
- Inventory systems for Electronic Judging System 1.0 deployments.
- Confirm whether /admin/edit_judge.php is reachable externally.
- Review application code for unsanitized judge_id database usage.
- Check logs for unusual requests targeting edit_judge.php.
- Verify compensating access controls around administrative routes.
Public sources used
Based on public source material and reviewed before publication.
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-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.
Open ATT&CK lookupCWE-89: Database access and collection lookup
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.
Open ATT&CK lookupDatabase behavior lookup
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.
Open ATT&CK lookupCVE-2026-9525 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
4 official scoresWe 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.
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 10 6.4 VulDB CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 3.9 3.4 VulDB CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 3.9 3.4 VulDB 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 — — VulDB Vulnerability scoring details
Base CVSS 4.0 score
6.9 MediumVector: 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 CVSS 3.1 score
7.3 HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 3.0 score
7.3 HighVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 2.0 score
7.5 HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline VulDB
Advisory disclosed
- Source timeline VulDB
VulDB entry created
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline VulDB
VulDB entry last update
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 source CVE List V5
- VDB-365544 | itsourcecode Electronic Judging System edit_judge.php sql injection CVE reference, VulDB · vdb-entry, technical-description
- VDB-365544 | CTI Indicators (IOB, IOC, TTP, IOA) CVE reference, VulDB · signature, permissions-required
- Submit #814713 | itsourcecode Electronic Judging System V1.0 SQL injection CVE reference, VulDB · third-party-advisory
- https://github.com/i-QvQ-i/first-OvO/issues/3 CVE reference, VulDB · exploit, issue-tracking
- https://itsourcecode.com/ CVE reference, VulDB · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.