dbcve.org
CourseselectionsystemApplication · Kidaze

CVE-2025-11052

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 security flaw has been discovered in kidaze CourseSelectionSystem 1.0/5.php. The impacted element is an unknown function of the file /Profilers/PriProfile/COUNT3s5.php. Performing manipulation of the argument csslc results in sql injection. The attack can be initiated remotely. The exploit has been released to the public and may be exploited.

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

A SQL injection vulnerability exists in kidaze CourseSelectionSystem 1.0 in the file /Profilers/PriProfile/COUNT3s5.php. The 'csslc' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) in COUNT3s5.php for the csslc parameter. If immediate patching is not possible, implement input validation and web application firewall rules as temporary mitigation.

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:all versions

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
    Search for the file /Profilers/PriProfile/COUNT3s5.php in your web server document root or application directory. Common paths include /var/www/html/, /www/, /htdocs/, or C:\inetpub\wwwroot\ on Windows servers.
    Affected if The file COUNT3s5.php exists in the application directory structure.
  2. Identify the web server root directory
    Check your web server configuration (Apache httpd.conf, Nginx.conf, or IIS Manager) to determine the document root where web-accessible files are served from.
    Affected if The document root points to a directory that contains the Profilers/PriProfile/COUNT3s5.php file.
  3. Verify the vulnerable parameter handling exists
    Open the file /Profilers/PriProfile/COUNT3s5.php in a text editor or use 'grep' to search for the 'csslc' parameter. Look for SQL query statements that include $_GET['csslc'] or $_POST['csslc'] without sanitization functions such as mysqli_real_escape_string, htmlspecialchars, or prepared statements.
    Affected if The file contains SQL queries using the csslc parameter directly from user input without proper escaping or parameterized queries.
  4. Check if the application is network-accessible
    Attempt to access the vulnerable endpoint via HTTP/HTTPS: GET /Profilers/PriProfile/COUNT3s5.php?csslc=test. Check your firewall rules, web server access logs, and application configuration to confirm the Profilers directory is publicly accessible.
    Affected if The application is reachable over the network and the COUNT3s5.php script executes when requested.
  5. Review database query logging
    Enable or review database query logs (MySQL general_log, PostgreSQL logging) while making a test request with the csslc parameter. Look for unauthenticated SQL queries being executed with unsanitized input.
    Affected if SQL queries are being executed with unsanitized csslc parameter values in the application database logs.

A user is affected if the Kidaze CourseSelectionSystem is installed with the COUNT3s5.php file present and the application is network-accessible, with the csslc parameter being used in SQL queries without 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries (prepared statements) in COUNT3s5.php for the csslc parameter. If immediate patching is not possible, implement input validation and web application firewall rules as temporary mitigation.

Fix this in Courseselectionsystem Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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