dbcve.org
Judging Management SystemApplication · Judging Management System Project

CVE-2023-37682

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Judging Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /php-jms/deductScores.php.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in Judging Management System v1.0 allows remote attackers to inject malicious SQL queries through the unprotected 'id' parameter in /php-jms/deductScores.php. The lack of input sanitization or parameterized queries enables complete database compromise, potentially exposing sensitive data or allowing privilege escalation.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries and implement strict input validation on all user-supplied parameters before database interaction.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Judging Management SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Judging Management System installation
    Locate the web application directory - typically found under /php-jms/ or similar web root paths. Look for application files including deductScores.php, login.php, and other PHP files typical of the Judging Management System.
    Affected if The application is installed and the vulnerable file exists in the web directory.
  2. Verify the application version
    Check for a version file, about page, or header/comment in PHP files that indicates the version. Common locations include a README file, config file, or the main index.php header comments.
    Affected if The installed version is Judging Management System v1.0.
  3. Locate the vulnerable deductScores.php file
    Navigate to the /php-jms/ directory and confirm the presence of deductScores.php. This is the specific file containing the SQL injection vulnerability.
    Affected if The file /php-jms/deductScores.php exists in the installation.
  4. Inspect the SQL query implementation in deductScores.php
    Open deductScores.php and examine the code handling the 'id' parameter. Look for SQL queries that directly incorporate the id parameter without using prepared statements, parameterized queries, or input sanitization.
    Affected if The code contains direct SQL queries using the 'id' parameter without prepared statements or sanitization functions like mysqli_prepare, PDO::prepare, or htmlspecialchars/real_escape_string.
  5. Test for SQL injection vulnerability (if authorized)
    If you have authorization, send a crafted request to /php-jms/deductScores.php with the id parameter set to a test payload such as '1' OR '1'='1 to observe if the application returns unexpected database errors or altered behavior.
    Affected if The application responds with SQL errors or returns different data than expected, confirming the parameter is vulnerable to SQL injection.

You are affected if the Judging Management System v1.0 is installed with the file /php-jms/deductScores.php present and the code shows direct use of the 'id' parameter in SQL queries without prepared statements or input sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with prepared statements/parameterized queries and implement strict input validation on all user-supplied parameters before database interaction.

Fix this in Judging Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37682 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data