dbcve.org
CourseselectionsystemApplication · Kidaze

CVE-2025-11032

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-26
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 flaw has been found in kidaze CourseSelectionSystem up to 42cd892b40a18d50bd4ed1905fa89f939173a464. This issue affects some unknown processing of the file /Profilers/PriProfile/COUNT3s6.php. Executing manipulation of the argument CPU can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed.

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 /Profilers/PriProfile/COUNT3s6.php file allows remote attackers to manipulate the CPU parameter to inject arbitrary SQL queries. The vulnerability has a CVSS score of 9.8 (Critical) indicating ease of exploitation and severe potential impact.

MitigationImplement parameterized queries or prepared statements for all database interactions involving the CPU parameter in COUNT3s6.php to eliminate SQL injection. If immediate patching is not possible, consider deploying a WAF rule to block SQL injection attempts targeting this endpoint.

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. Confirm kidaze CourseSelectionSystem is installed
    Identify if this web application is present on the server by checking for its installation directory, default web root paths, or by reviewing web server configurations for sites running this software.
    Affected if The software is present on the server.
  2. Locate the vulnerable COUNT3s6.php file
    Search the web directory for the file at path /Profilers/PriProfile/COUNT3s6.php or inspect the application's file structure for this specific PHP file.
    Affected if The file COUNT3s6.php exists in the /Profilers/PriProfile/ directory.
  3. Check the installed software version
    Review version information from the application header, readme files, or database configuration files to determine the build date or version. Compare against the affected version <= 2017-06-18.
    Affected if The installed version is dated 2017-06-18 or earlier.
  4. Inspect CPU parameter handling in COUNT3s6.php
    Open COUNT3s6.php and examine how the CPU parameter is processed. Look for database queries that incorporate the CPU parameter directly without using prepared statements or parameterized queries.
    Affected if The CPU parameter is used in SQL queries without parameterized binding (e.g., direct string concatenation or interpolation).

The environment is affected if kidaze CourseSelectionSystem is installed, the file /Profilers/PriProfile/COUNT3s6.php exists, and the CPU parameter in that file is handled in SQL queries without prepared statement binding.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2017-06-18
Interim mitigation

Implement parameterized queries or prepared statements for all database interactions involving the CPU parameter in COUNT3s6.php to eliminate SQL injection. If immediate patching is not possible, consider deploying a WAF rule to block SQL injection attempts targeting this endpoint.

Recommended fix Moderate confidence

latest rolling release (clone/pull current main/HEAD branch)

  1. 1. Navigate to the kidaze CourseSelectionSystem GitHub repository (github.com/kidaze/CourseSelectionSystem)
  2. 2. Clone or pull the latest code from the repository to ensure you have the most recent rolling release
  3. 3. Locate the file /Profilers/PriProfile/COUNT3s6.php in the updated codebase
  4. 4. Verify that the SQL injection vulnerability in the CPU parameter has been addressed - the parameter should now use parameterized queries or proper input sanitization
  5. 5. Replace the vulnerable file on your production server with the updated version
  6. 6. Test the application to ensure the course selection functionality still works correctly after the update
  7. 7. Monitor for any unusual database activity or errors

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Courseselectionsystem Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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