dbcve.org
CourseselectionsystemApplication · Kidaze

CVE-2025-10477

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to after 2017-06-18 or later.
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
A vulnerability was identified in kidaze CourseSelectionSystem up to 42cd892b40a18d50bd4ed1905fa89f939173a464. The affected element is an unknown function of the file /Profilers/PriProfile/eligibility.php. Such manipulation of the argument Branch leads to sql injection. The attack can be launched remotely. The exploit is publicly available and might be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable.

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 kidaze CourseSelectionSystem's eligibility.php file allows remote attackers to inject malicious SQL queries via the Branch parameter. The critical CVSS score of 9.8 indicates the flaw is easily exploitable over the network and can lead to unauthorized database access, data exfiltration, or potentially remote code execution depending on database configuration.

MitigationImplement prepared statements/parameterized queries for all database operations in eligibility.php, particularly for the Branch parameter. Apply input validation and sanitization as an additional defense layer, and restrict network access to administrative functions.

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. Locate the Kidaze CourseSelectionSystem installation
    Search for the eligibility.php file in your web server directories (commonly under /var/www/html, /www, or the document root) using: find / -name 'eligibility.php' 2>/dev/null
    Affected if The file is found in the system, indicating the application is installed
  2. Verify the application version
    Check the application version by reviewing any version file, README, or metadata in the installation directory. If no version file exists, check file modification dates: ls -la eligibility.php
    Affected if The version or file date is on or before 2017-06-18, indicating a potentially vulnerable release
  3. Inspect the Branch parameter handling in eligibility.php
    Examine eligibility.php for direct use of the Branch parameter in SQL queries without prepared statements. Look for patterns like: $Branch = $_GET['Branch']; followed by a SQL query containing $Branch
    Affected if The Branch parameter is used in SQL queries without parameterization (no prepare() or bindParam() calls)
  4. Check if the application is exposed to the network
    Verify the web server configuration exposes the eligibility.php file to network access. Check firewall rules or web server vhost configurations for the path to eligibility.php
    Affected if The file is accessible over the network (not localhost-only or firewalled)
  5. Identify database user privileges
    Review database connection configuration in the application (typically in a config.php or db.php file) to determine if the database user has elevated privileges beyond SELECT
    Affected if The database user has privileges beyond read-only (INSERT, UPDATE, DROP, or EXECUTE), increasing attack impact

A system is affected if the Kidaze CourseSelectionSystem is installed with eligibility.php dated on or before 2017-06-18, the Branch parameter is used in unprotected SQL queries, and the file is network-accessible.

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

Implement prepared statements/parameterized queries for all database operations in eligibility.php, particularly for the Branch parameter. Apply input validation and sanitization as an additional defense layer, and restrict network access to administrative functions.

Fix this in Courseselectionsystem Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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