dbcve.org
CourseselectionsystemApplication · Kidaze

CVE-2025-10597

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-17
Fix available
A fix is available. Upgrade to after 2017-06-18 or later.
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 vulnerability was determined in kidaze CourseSelectionSystem up to 42cd892b40a18d50bd4ed1905fa89f939173a464. This vulnerability affects unknown code of the file /Profilers/PriProfile/COUNT2.php. This manipulation of the argument cname causes sql injection. The attack may be initiated remotely. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available.

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 kidaze CourseSelectionSystem's /Profilers/PriProfile/COUNT2.php file via the 'cname' parameter allows remote attackers to inject malicious SQL queries. The vulnerability has a CVSS score of 9.8 (Critical) indicating complete potential compromise of the database.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in COUNT2.php and implement proper input validation on the 'cname' parameter. Consider implementing a web application firewall as an additional layer of defense.

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
CourseselectionsystemApplication
Affected:<= 2017-06-18

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 Kidaze CourseSelectionSystem installation
    Locate the web application directory and confirm it is the Kidaze CourseSelectionSystem by searching for identifying files such as login pages, configuration files, or application-specific assets that contain 'kidaze' or 'courseselection' branding.
    Affected if The application directory cannot be identified as Kidaze CourseSelectionSystem.
  2. Determine the installed version
    Check for version information in the application such as a version file, footer text, or configuration metadata. Compare the version or build date against the affected range (2017-06-18 and earlier).
    Affected if The installed version is dated 2017-06-18 or earlier, or the version number is <= the affected release.
  3. Verify the vulnerable file exists
    Check for the presence of /Profilers/PriProfile/COUNT2.php within the web application directory structure.
    Affected if The file COUNT2.php does not exist in the expected path.
  4. Confirm the cname parameter is accessible
    Attempt to access the COUNT2.php endpoint via HTTP and verify the cname parameter is accepted as user input (for example, by sending a test request with a benign value).
    Affected if The endpoint returns an error indicating the parameter is not expected or is rejected.
  5. Inspect code for unsanitized SQL usage
    Review the source code of COUNT2.php and locate where the cname parameter is used in SQL queries. Verify if the parameter is passed directly to the database without parameterized queries, prepared statements, or input sanitization.
    Affected if The cname parameter is concatenated directly into SQL queries without escaping, binding, or validation.

A user is affected if they run Kidaze CourseSelectionSystem version 2017-06-18 or earlier with the COUNT2.php file present and the cname parameter handled without parameterized queries in the SQL logic.

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
Upgrade available Upgrade to a release after 2017-06-18
Interim mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in COUNT2.php and implement proper input validation on the 'cname' parameter. Consider implementing a web application firewall as an additional layer of defense.

Fix this in Courseselectionsystem Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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