dbcve.org
Student Result Management SystemApplication · Munyweki

CVE-2026-2983

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-23
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 determined in SourceCodester Student Result Management System 1.0. The impacted element is an unknown function of the file /admin/core/import_users.php of the component Bulk Import. This manipulation of the argument File causes improper access controls. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.

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

The vulnerability exists in the Bulk Import function of /admin/core/import_users.php in SourceCodester Student Result Management System 1.0. The 'File' argument lacks proper access controls, allowing unauthorized users to potentially access or manipulate files they should not have permission to access. The critical CVSS score indicates this is easily exploitable remotely with complete impact.

MitigationImplement proper authentication and authorization checks on the bulk import endpoint to verify user permissions before processing file arguments. Additionally, validate and sanitize the File parameter to prevent unauthorized file access or path traversal.

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
Student Result 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. Confirm the application is installed
    Locate the file /admin/core/import_users.php on the web server filesystem or check if the application responds at the expected URL path.
    Affected if The file exists and the application is running.
  2. Verify the application version
    Access the application and identify the installed version. Compare against the affected version: Munyweki Student Result Management System = 1.0.
    Affected if The installed version is 1.0.
  3. Check admin area access controls
    Attempt to access the /admin/core/import_users.php endpoint directly without providing authentication credentials or a valid session cookie.
    Affected if The page loads or responds without requiring login.
  4. Inspect the File parameter handling
    Examine the import_users.php source code and look for access control checks (such as session verification, role checks, or permission validation) before processing the File argument.
    Affected if No authentication or authorization checks are present before the File parameter is processed.
  5. Test for unauthorized file access
    Send a request to import_users.php with a manipulated File parameter pointing to a file outside the intended directory (e.g., ../../etc/passwd or ../../config.php).
    Affected if The application returns content from files outside the expected upload directory or reveals sensitive file contents.

A user is affected if the application is version 1.0 and the /admin/core/import_users.php endpoint is accessible without authentication and processes the File parameter without authorization checks.

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 proper authentication and authorization checks on the bulk import endpoint to verify user permissions before processing file arguments. Additionally, validate and sanitize the File parameter to prevent unauthorized file access or path traversal.

Fix this in Student Result Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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