dbcve.org
CourseselectionsystemApplication · Kidaze

CVE-2025-11033

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 vulnerability has been found in kidaze CourseSelectionSystem up to 42cd892b40a18d50bd4ed1905fa89f939173a464. Impacted is an unknown function of the file /Profilers/PriProfile/COUNT3s7.php. The manipulation of the argument cbe leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are 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/COUNT3s7.php file via the 'cbe' parameter allows remote attackers to inject malicious SQL queries. The vulnerability has a critical CVSS score of 9.8 and a public exploit is available.

MitigationImplement parameterized queries or prepared statements for all database operations using the 'cbe' parameter. Apply input validation and ensure database accounts use least privilege. Since this is a rolling-release product, contact the vendor for update availability.

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 Kidaze CourseSelectionSystem installation
    Search the web root directory for the presence of 'COUNT3s7.php' file in the path /Profilers/PriProfile/ or search for files containing 'CourseSelectionSystem' or 'kidaze' in the application directory structure.
    Affected if The file /Profilers/PriProfile/COUNT3s7.php exists in the web application's directory structure.
  2. Determine installed version
    Check for version information in application metadata files (such as version.php, changelog, or readme files in the installation root), or inspect the application's admin panel for version details. Compare the found version or build date to the affected release date of 2017-06-18.
    Affected if The installed version is dated on or before 2017-06-18, or the version number indicates a release prior to the patched version.
  3. Verify vulnerable parameter is accessible
    Attempt to access the URL endpoint /Profilers/PriProfile/COUNT3s7.php directly via HTTP request and check if the 'cbe' parameter is accepted as a query parameter.
    Affected if The page responds and accepts the 'cbe' parameter without requiring authentication or when accessed via the application's normal flow.
  4. Confirm SQL injection point exists
    Send a test request with a benign SQL payload in the 'cbe' parameter (e.g., 'cbe=1' AND '1'='1) and observe if the application returns database errors or unexpected behavior indicating SQL injection.
    Affected if The application returns SQL syntax errors, database error messages, or exhibits time delays consistent with blind SQL injection when the parameter is manipulated.

The environment is affected if Kidaze CourseSelectionSystem is installed with a version dated on or before 2017-06-18 and the /Profilers/PriProfile/COUNT3s7.php file exists and accepts the 'cbe' parameter without proper 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
Upgrade available Upgrade to a release after 2017-06-18
Interim mitigation

Implement parameterized queries or prepared statements for all database operations using the 'cbe' parameter. Apply input validation and ensure database accounts use least privilege. Since this is a rolling-release product, contact the vendor for update availability.

Fix this in Courseselectionsystem 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 the upgrade done

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-11033 — 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-11033 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