dbcve.org
School Management SystemApplication · Oranbyte

CVE-2025-11658

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-13
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 vulnerability was detected in ProjectsAndPrograms School Management System up to 6b6fae5426044f89c08d0dd101c7fa71f9042a59. Affected is an unknown function of the file /assets/changeSllyabus.php. The manipulation of the argument File results in unrestricted upload. The attack may be launched remotely. The exploit is now public and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases.

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 ProjectsAndPrograms School Management System allows remote attackers to upload arbitrary files via the /assets/changeSllyabus.php endpoint using the 'File' parameter. The lack of proper input validation and file type checking enables attackers to upload malicious files (e.g., PHP webshells) and potentially achieve remote code execution on the server.

MitigationImplement strict file upload validation including allowlist-based file extension checking, MIME type verification, magic byte validation, and store uploaded files outside the web root with random filenames. Additionally, disable PHP execution in upload directories and implement proper authentication/authorization checks on the affected 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
School Management SystemApplication
Affected:= 1.0

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. Verify Oranbyte School Management System version
    Locate version information in the application by checking the footer, about page, or version file in the installation directory. Compare against version 1.0.
    Affected if The installed version is Oranbyte School Management System version 1.0.
  2. Confirm vulnerable endpoint exists
    Check if the file /assets/changeSllyabus.php exists on the web server. This can be done via file system inspection of the web root directory or by checking for a 200/403 response when accessing the URL.
    Affected if The endpoint /assets/changeSllyabus.php is present on the server.
  3. Check if upload functionality is accessible
    Inspect the changeSllyabus.php file to determine if the 'File' parameter handling code allows unauthenticated or improperly authenticated access to the file upload mechanism.
    Affected if The endpoint accepts file uploads without proper authentication or authorization controls.
  4. Examine file validation logic
    Review the code in changeSllyabus.php to identify if there is proper file type checking, extension allowlisting, or content-type validation before saving uploaded files.
    Affected if The code lacks proper input validation, extension allowlisting, or MIME type verification for uploaded files.
  5. Verify upload directory configuration
    Check if uploaded files are stored within the web root and whether PHP execution is disabled in the upload directory.
    Affected if Files are stored inside the web root and PHP execution is allowed in the upload directory.

A system is affected if it runs Oranbyte School Management System version 1.0 and contains the /assets/changeSllyabus.php endpoint with unrestricted file upload capability.

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 file upload validation including allowlist-based file extension checking, MIME type verification, magic byte validation, and store uploaded files outside the web root with random filenames. Additionally, disable PHP execution in upload directories and implement proper authentication/authorization checks on the affected endpoint.

Fix this in School Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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