CVE-2026-9525
Deferred Deferred - Pending Action
SQL Injection in Electronic Judging System

Publication date: 2026-05-26

Last updated on: 2026-05-26

Assigner: VulDB

Description
A vulnerability has been found in itsourcecode Electronic Judging System 1.0. This affects an unknown part of the file /admin/edit_judge.php. The manipulation of the argument judge_id leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-26
Last Modified
2026-05-26
Generated
2026-06-15
AI Q&A
2026-05-26
EPSS Evaluated
2026-06-14
NVD
CVE-2026-9525
EUVD
EUVD-2026-31784
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
itsourcecode electronic_judging_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-9525 is a SQL injection vulnerability found in the itsourcecode Electronic Judging System version 1.0. It specifically affects the /admin/edit_judge.php file where the judge_id parameter is not properly validated. This allows an attacker to inject malicious SQL code remotely without needing to authenticate.

By exploiting this flaw, attackers can manipulate the database queries executed by the system, potentially gaining unauthorized access to data or altering the database.

Compliance Impact

The SQL injection vulnerability in the Electronic Judging System allows unauthorized access to the database, which can lead to data tampering, sensitive information leakage, and system control by attackers.

Such unauthorized access and potential data breaches can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and breaches.

Failure to remediate this vulnerability could result in violations of these regulations due to compromised confidentiality, integrity, and availability of protected data.

Impact Analysis

This vulnerability can have serious impacts including unauthorized access to the database, data tampering, leakage of sensitive information, and even gaining control over the system.

Attackers can exploit this vulnerability remotely without any login credentials, using various SQL injection techniques such as boolean-based blind, stacked queries, time-based blind, and UNION queries.

The exploitation may also lead to service disruption and compromise the integrity and availability of the system.

Detection Guidance

This vulnerability can be detected by testing the /admin/edit_judge.php endpoint for SQL injection via the judge_id parameter. Since the exploit does not require authentication, you can attempt to inject SQL payloads to observe abnormal behavior or database errors.

  • Use curl or similar tools to send crafted requests to the vulnerable URL, for example: curl "http://targetsite/admin/edit_judge.php?judge_id=1' OR '1'='1"
  • Use sqlmap to automate detection and exploitation: sqlmap -u "http://targetsite/admin/edit_judge.php?judge_id=1" --batch
  • Monitor network traffic for suspicious requests targeting /admin/edit_judge.php with unusual or malformed judge_id parameters.
Mitigation Strategies

Immediate mitigation steps include implementing proper input validation and using prepared statements or parameterized queries to prevent SQL injection.

  • Sanitize and validate all inputs, especially the judge_id parameter, to ensure only expected values are processed.
  • Refactor the code in /admin/edit_judge.php to use prepared statements instead of directly embedding user input in SQL queries.
  • Limit database user permissions to the minimum required to reduce the impact of a potential exploit.
  • Conduct regular security audits and code reviews to identify and fix similar vulnerabilities.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-9525. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart