dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-10777

HIGH · 7.3 CVSS v3.1 Published 2026-06-03
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 vulnerability was identified in ealpha072 Student-Management-System up to 01451bd7a2f58cdda07bd0b86e3967582e3ecd08. Affected by this issue is some unknown functionality of the file admin/config.php of the component Administrative Backend. Such manipulation leads to improper authentication. The attack may be performed from remote. The exploit is publicly available and might be used. 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 ealpha072 Student-Management-System contains an authentication bypass vulnerability in the administrative backend file admin/config.php. An attacker can exploit unknown functionality in this component to bypass authentication controls and gain unauthorized access to the admin panel. A publicly available exploit increases the likelihood of active targeting.

MitigationImplement proper authentication enforcement in admin/config.php and all admin backend functions. Since this is a rolling-release product with no patch available, consider disabling the affected administrative backend until the vendor responds, or implement compensating controls such as IP restriction or additional authentication layers at the network/Proxy level.

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. Locate the Student-Management-System installation
    Search the web server document root for files named 'config.php' within an 'admin' directory, or look for the string 'ealpha072' in PHP source files. Common paths include /admin/config.php, /student-management/admin/config.php, or similar web-accessible directories.
    Affected if The admin/config.php file from ealpha072 Student-Management-System exists on the server and is web-accessible.
  2. Verify administrative backend is accessible
    Attempt to access the admin/config.php file directly via HTTP/HTTPS request without providing any authentication credentials. For example: GET https://target.example.com/admin/config.php
    Affected if The page loads or responds without redirecting to a login form or returning an authentication error.
  3. Inspect authentication logic in admin/config.php
    Open admin/config.php in a text editor and examine the code near the top of the file. Look for conditional statements that control access, such as checks for session variables, cookies, or authentication flags. Pay particular attention to any conditions that may be easily bypassed (e.g., commented-out checks, hardcoded bypass conditions, or missing include statements for auth libraries.
    Affected if The authentication logic contains flaws such as missing authentication checks, commented-out security code, or conditional statements that can be trivially circumvented.
  4. Check for unauthenticated administrative function access
    Send HTTP requests to known administrative endpoints (e.g., /admin/, /admin/dashboard.php, /admin/users.php) without providing valid credentials. Observe whether the application grants access or exposes sensitive administrative functionality.
    Affected if Administrative functions are accessible and operational without any form of authentication.

The environment is affected if the ealpha072 Student-Management-System is deployed with its admin/config.php file accessible via the web and the authentication mechanism in that file can be bypassed to gain unauthorized administrative access.

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 enforcement in admin/config.php and all admin backend functions. Since this is a rolling-release product with no patch available, consider disabling the affected administrative backend until the vendor responds, or implement compensating controls such as IP restriction or additional authentication layers at the network/Proxy level.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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