Skip to main content
CVE-2023-30014VulnerabilityPublished Updated

CVE-2023-30014: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
n/a n/aAffected
  • =1.0
Fixed in–

AI-suggested

Given the absence of official patches, European organizations should immediately implement the following mitigations: 1) Restrict access to the 'sub_event_stat_update.php' endpoint by applying network-level controls such as IP whitelisting or VPN access to limit exposure to trusted users only. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'sub_event_id' parameter. 3) Conduct thorough input validation and sanitization on all parameters, especially 'sub_event_id', to ensure only expected data types and values are accepted. 4) Monitor logs for unusual database queries or repeated failed attempts to exploit the parameter. 5) If possible, isolate the Judging Management System in a segmented network zone to minimize lateral movement in case of compromise. 6) Prepare for incident response by backing up databases securely and testing restoration procedures. 7) Engage with the software vendor or community to seek or contribute to patch development and updates. These steps go beyond generic advice by focusing on immediate containment, detection, and preparation in the absence of vendor patches.

Description

SQL Injection vulnerability in oretnom23 Judging Management System v1.0, allows remote attackers to execute arbitrary code and obtain sensitive information via sub_event_id parameter in sub_event_stat_update.php.

References

Community reviews

Loading reviews…