CVE-2026-9528
BaseFortify
Publication date: 2026-05-26
Last updated on: 2026-05-26
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| itsourcecode | electronic_judging_system | 1.0 |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-9528 is a SQL injection vulnerability in the Electronic Judging System Project V1.0, specifically in the file /admin/delete_judge.php. It occurs because the judge_id parameter is not properly validated, allowing attackers to inject malicious SQL queries.
This vulnerability can be exploited remotely without authentication, enabling unauthorized access to the database.
A proof-of-concept payload such as judge_id=4'or sleep(2)--+ can demonstrate the vulnerability by causing a delayed response.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data tampering, leakage of sensitive information, and potential system compromise.
It can cause severe security risks including data breaches and service disruption.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the `judge_id` parameter in the `/admin/delete_judge.php` file for injection flaws.
A proof-of-concept payload such as `judge_id=4'or sleep(2)--+` can be used to detect the vulnerability by observing a delayed response, indicating successful SQL injection.
You can use tools like curl or Burp Suite to send requests with this payload and monitor response times.
- Example curl command: curl "http://targetsite/admin/delete_judge.php?judge_id=4'or sleep(2)--+" -v
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Use prepared statements with parameter binding to prevent SQL injection.
- Implement strict input validation on the `judge_id` parameter.
- Minimize database user permissions to limit potential damage.
- Conduct regular security audits to identify and fix vulnerabilities.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Electronic Judging System allows unauthorized access to the database, leading to potential data breaches, data tampering, and leakage of sensitive information.
Such security risks can result in non-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 mitigate this vulnerability could therefore expose organizations to legal and regulatory consequences due to compromised data confidentiality and integrity.