Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-14719

HIGH · 7.3 CVSS v3.1 Published 2026-07-05
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 7 weeks old

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 flaw has been found in SourceCodester Onlne Examination & Learning Management System 1.0. The impacted element is an unknown function of the file register.php of the component Registration Endpoint. Executing a manipulation of the argument role can lead to improper privilege management. The attack can be executed remotely. The exploit has been published and may be used. The name of the affected product appears to have a typo in it.

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 registration endpoint in register.php of SourceCodester Online Examination & Learning Management System 1.0 allows remote attackers to manipulate the 'role' argument during user registration, enabling improper privilege escalation. This appears to be a broken access control vulnerability where the application does not properly validate or authorize the role parameter, potentially allowing attackers to register as administrative users.

MitigationImplement strict server-side validation of the role parameter, ensuring only predefined valid roles are accepted and enforcing proper authorization checks before assigning privileges. Remove any client-side role specification from the registration process.

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. Confirm product and version
    Identify the installed version of SourceCodester Online Examination & Learning Management System. Check application documentation, about page, or system files for version number '1.0'.
    Affected if The system is running version 1.0 of SourceCodester Online Examination & Learning Management System
  2. Locate registration endpoint
    Verify that register.php exists in the web root or accessible path of the application.
    Affected if register.php is present and accessible without authentication
  3. Inspect registration form or API request
    Access the registration page or capture a registration request using browser dev tools or proxy. Examine if a 'role' parameter or field is present in the form or request.
    Affected if A 'role' parameter, field, or hidden input is included in the registration functionality
  4. Test role parameter manipulation
    Submit a registration request with a modified 'role' parameter set to an administrative value (such as 'admin', 'administrator', or '1'). Observe if the application accepts and processes this parameter.
    Affected if The application accepts and processes the role parameter without server-side validation or rejects it silently (both indicate lack of proper access control)
  5. Verify server-side role validation
    Review server-side code in register.php (or equivalent) to check if the role parameter is validated against an allowed list, or check if role assignment is hardcoded to a default low-privilege value.
    Affected if No server-side validation exists, or role can be set arbitrarily from user input

A system is affected if it runs SourceCodester Online Examination & Learning Management System 1.0 and allows the role parameter to be manipulated during registration without proper server-side validation.

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 server-side validation of the role parameter, ensuring only predefined valid roles are accepted and enforcing proper authorization checks before assigning privileges. Remove any client-side role specification from the registration process.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-14719 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