dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-11532

MEDIUM · 6.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 →
69/100
Remediation priority · Elevated
Remotely reachable 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 weakness has been identified in imvks786 student_management_system up to 9599b560ad3c3b83e75d328b76bedcd489ef1f46. Affected is an unknown function of the file /add.php of the component Student Record Handler. Executing a manipulation can lead to improper access controls. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. 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 · moderate confidence

The student_management_system contains an improper access control vulnerability in /add.php (Student Record Handler component). Remote attackers can manipulate student records without authentication or proper authorization, as the affected endpoint lacks adequate access control checks.

MitigationImplement proper authentication and role-based authorization checks on the /add.php endpoint to ensure only authorized personnel can add or modify student records.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate the student record handler add.php file
    Search the web server document root for files named 'add.php' in directories related to student records, enrollment, or academic systems. Common paths may include /student/, /records/, /academic/, or similar educational application directories.
    Affected if The file /add.php exists in a student record management application and is accessible via HTTP/HTTPS requests.
  2. Verify if the endpoint accepts unauthenticated requests
    Send an HTTP GET or POST request to the add.php endpoint without providing any session cookies, authentication tokens, or login credentials. Inspect the HTTP response status and content.
    Affected if The server returns a successful response (2xx status) instead of redirecting to a login page or returning 401/403 authentication errors.
  3. Inspect the source code for authorization logic
    Open the add.php file and search for authorization-related function calls such as 'session_start()', 'isLoggedIn()', 'checkAuth()', 'verifyRole()', 'hasPermission()', or role-based access control (RBAC) checks. Also look for $_SESSION variable checks before processing form data.
    Affected if The add.php file lacks function calls that verify user authentication or authorization before processing student record data, or such checks are present but conditionally bypassed.
  4. Test for broken access control by submitting a record add request
    Send a POST request to add.php with typical student record parameters (such as student name, ID, grade, or course enrollment data) without any authentication. Compare the response and any database changes against authorized requests.
    Affected if The record is successfully added or the application processes the request without returning an authorization error, indicating missing access controls.
  5. Check for role-based access enforcement
    Examine the code for role validation logic that restricts the add operation to privileged roles (such as admin, registrar, or instructor). Look for conditional statements that check user roles or permissions before allowing record creation.
    Affected if No role or privilege checks exist in add.php, or the code relies solely on hidden form fields or client-side checks rather than server-side authorization.

A user is affected if the /add.php file exists in their student record system, is accessible without authentication, and lacks proper server-side authorization checks before allowing record manipulation.

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 role-based authorization checks on the /add.php endpoint to ensure only authorized personnel can add or modify student records.

Have this fixed 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-2026-11532 — 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-11532 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