Safeguard
Vulnerability Analysis•

CVE-2023-30014: Critical SQL Injection in Judging Management System

CVE-2023-30014 is a Critical (CVSS 9.8) SQL injection in Judging Management System 1.0 via sub_event_stat_update.php. No fix known, so remove or rework it.

Safeguard Security Team
3 min read

CVE-2023-30014 is a critical severity (CVSS 9.8) SQL injection in Judging Management System version 1.0 by oretnom23. The sub_event_id input of sub_event_stat_update.php reaches a database query unsafely. No vendor fix is confirmed, so take the app off untrusted networks and replace or fix the code.

What's affected

The NVD record lists oretnom23 Judging Management System 1.0. The vulnerable file is sub_event_stat_update.php and the parameter is sub_event_id. No fixed version is named in the record or in the researcher write-up we retrieved, so assume every copy of this version is affected and check with the code's author for any update.

This is a small PHP project, the kind people download and run as a school or event tool. The record does not say how many installations exist.

How to check if you're exposed

Search your servers and repositories for the application, then confirm whether the file named above exists. On a Linux host you can run this command from the web root:

find . -name sub_event_stat_update.php

If the file exists and the site is reachable from the internet, treat it as exposed. Safeguard's free in-browser scan at https://gold.safeguard.sh/scan can also check the dependency manifests of your own projects for known issues.

What to do now

  1. Find any running copy of Judging Management System and who owns it.
  2. Take it off the public internet, or put it behind a VPN or an authentication layer you control.
  3. Rewrite the affected query with parameterized statements, or replace the application with a maintained one.
  4. Review the database for signs of unwanted reads or changes, and rotate any credentials stored in it.

Why it matters

SQL injection, CWE-89, is one of the oldest weaknesses on the web. User input is joined into a query string, so the database cannot tell data from instructions. The fix is the same as it has been for years: parameterized queries, strict input handling, and a database account with only the rights the app needs.

The record scores this 9.8 because it is reachable over the network without privileges. The NVD description mentions code execution and information disclosure. The public write-up we read for the first issue shows database content being disclosed, so plan for data exposure at minimum. This write-up is for this CVE. The CVE is not on the CISA KEV list.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Is there a patch?

None is named in the record. Plan to fix the code yourself or retire the app.

Why is the score so high?

The flaw is reachable over the network with no login, and the possible impact on confidentiality, integrity and availability is rated high.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.