CVE-2025-9765
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 · uneditedA vulnerability has been found in itsourcecode Sports Management System 1.0. The affected element is an unknown function of the file /Admin/tournament_details.php. Such manipulation of the argument ID leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.
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 confidenceSQL injection vulnerability in the ID parameter of /Admin/tournament_details.php in itsourcecode Sports Management System 1.0 allows remote attackers to execute arbitrary SQL commands via unsanitized user input.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Sports Management System versionInspect the application source code, typically found in the web root directory. Look for version indicators in README files, about pages, or the main index file. Check footer or meta tags for version information.Affected if The installed version is Angeljudescuarez Sports Management System 1.0 or if the software matches the itsourcecode Sports Management System without confirmed remediation.
-
Verify vulnerable file existsCheck for the presence of /Admin/tournament_details.php in the web application directory. This file should exist in a directory named Admin or administrator within the web root.Affected if The file /Admin/tournament_details.php exists in the web application.
-
Confirm admin endpoint accessibilityAttempt to access the /Admin/ path via HTTP request to determine if the administrative interface is publicly or internally accessible. Check web server configuration for routing to this directory.Affected if The /Admin/ directory and its contents are accessible from the network where the application is hosted.
-
Check for unsanitized ID parameter usageReview the source code of tournament_details.php and locate the SQL query handling the ID parameter. Search for dynamic SQL construction (string concatenation or string formatting in SQL queries) without use of prepared statements or parameterized queries.Affected if The code constructs SQL queries using the ID parameter through string concatenation or interpolation without input sanitization or prepared statements.
A system is affected if it runs Angeljudesuarez Sports Management System 1.0 with the vulnerable /Admin/tournament_details.php file accessible and the ID parameter processed through unsanitized dynamic SQL queries.
Generated from the published advisory. Verify against your own configuration.
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 dataRemediate by replacing dynamic SQL query construction with parameterized queries (prepared statements) and implementing proper input validation on the ID parameter.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9765 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9765 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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