dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-11474

HIGH · 7.3 CVSS v3.1 Published 2026-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Kushan2k student-management-system up to f16a4ceaddd6729c4b306ed4641cda3176c1ef2a. Affected is an unknown function of the file service/RegisterService.php of the component Registration Endpoint. Performing a manipulation of the argument stimg results in unrestricted upload. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. 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. The project was informed of the problem early through an issue report but has not responded yet.

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

Unrestricted file upload vulnerability in the Registration Endpoint of Kushan2k student-management-system (service/RegisterService.php). The 'stimg' argument accepts arbitrary file uploads without validation, allowing attackers to upload malicious files that could lead to remote code execution.

MitigationImplement strict allowlist-based file type validation, enforce file size limits, store uploads outside the web root with randomized filenames, and add proper authentication/authorization checks on the registration endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 if Kushan2k student-management-system is installed
    Search for the presence of the student-management-system codebase, typically in web root directories. Look for folders named 'student-management-system', 'kushan2k', or similar naming conventions. Check for the file service/RegisterService.php in the application structure.
    Affected if The Kushan2k student-management-system is found installed in the environment.
  2. Locate the vulnerable RegisterService.php file
    Navigate to the service/ directory within the application and confirm RegisterService.php exists. Open the file and search for the 'stimg' parameter handling logic.
    Affected if The file service/RegisterService.php exists and contains code handling the 'stimg' parameter.
  3. Inspect file validation logic in RegisterService.php
    Examine the code handling the 'stimg' parameter for any file type validation, MIME type checking, extension allowlisting, or content validation. Look for functions like mime_content_type, getimagesize, or extension checks.
    Affected if The 'stimg' parameter processing lacks proper file type validation, MIME type verification, or extension allowlisting.
  4. Check if registration endpoint is accessible without authentication
    Determine if the registration endpoint (typically /register or the RegisterService.php endpoint) can be accessed without requiring authentication. Review the application's authentication configuration and endpoint access controls.
    Affected if The registration endpoint is publicly accessible without requiring authentication.
  5. Verify upload directory configuration
    Check if uploaded files are stored within the webroot and if script execution is enabled in the upload directory. Look for .htaccess or server configuration that may disable PHP/script execution in upload folders.
    Affected if Uploads are stored within the webroot and script execution is not disabled in the upload directory.

A user is affected if the Kushan2k student-management-system is installed with the service/RegisterService.php file present and the 'stimg' parameter lacks server-side file type validation while being accessible without authentication.

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

Implement strict allowlist-based file type validation, enforce file size limits, store uploads outside the web root with randomized filenames, and add proper authentication/authorization checks on the registration endpoint.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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