dbcve.org
Sports Management SystemApplication · Angeljudesuarez

CVE-2025-9840

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-02
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
Public exploit 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
A weakness has been identified in itsourcecode Sports Management System 1.0. The impacted element is an unknown function of the file /Admin/gametype.php. Executing manipulation of the argument code can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be exploited.

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 · high confidence

SQL injection vulnerability in itsourcecode Sports Management System 1.0 allows remote attackers to inject malicious SQL queries through the 'code' parameter in /Admin/gametype.php. The lack of input sanitization or parameterized queries enables unauthenticated attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or complete system compromise.

MitigationImplement prepared statements/parameterized queries for all database interactions, particularly in /Admin/gametype.php, and apply input validation and output encoding for the 'code' parameter and all user-supplied data.

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
Sports 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. Identify the installed application
    Locate and inspect the web application's main directory. Look for files or metadata indicating 'Sports Management System' or 'itsourcecode' branding. Check page footers, title tags, or version files for product identification.
    Affected if The application is Sports Management System by itsourcecode or Angeljudesuarez
  2. Confirm the version number
    Inspect version files, changelogs, or admin panels to determine the exact installed version. Compare against the affected version range.
    Affected if The installed version is exactly 1.0
  3. Verify the vulnerable file exists
    Check the web root for the presence of /Admin/gametype.php. This file handles game type management and contains the vulnerable 'code' parameter endpoint.
    Affected if The file /Admin/gametype.php exists in the application directory
  4. Check if the code parameter is processed
    Open /Admin/gametype.php and locate the code where the 'code' parameter is used in database queries. Look for direct insertion of $_POST or $_GET['code'] into SQL statements without prepared statements or sanitization functions.
    Affected if The 'code' parameter is directly used in SQL queries without parameterized queries or input sanitization
  5. Inspect database interaction patterns
    Review the database connection and query execution code in gametype.php. Look for mysqli_query(), mysql_query(), or PDO::query() calls where user input flows directly into the query string.
    Affected if Database queries use string concatenation with the 'code' parameter rather than binding parameters

You are affected if the Sports Management System version 1.0 is installed and /Admin/gametype.php processes the 'code' parameter 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

Implement prepared statements/parameterized queries for all database interactions, particularly in /Admin/gametype.php, and apply input validation and output encoding for the 'code' parameter and all user-supplied data.

Fix this in Sports Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9840 — 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-2025-9840 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