Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-12529

HIGH · 7.3 CVSS v3.1 Published 2026-06-17
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 security vulnerability has been detected in SourceCodester CET Automated Grading System with AI Predictive Analytics 1.0. Affected is an unknown function of the file /index.php of the component Student Self-Registration Endpoint. The manipulation leads to improper access controls. Remote exploitation of the attack is possible.

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

Improper access control vulnerability in the Student Self-Registration Endpoint of the SourceCodester CET Automated Grading System 1.0 allows remote attackers to bypass authentication/authorization checks via unknown manipulation of the /index.php file.

MitigationImplement proper authentication and role-based access control (RBAC) for the registration endpoint, including validation that users have appropriate permissions before allowing self-registration actions.

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 the SourceCodester CET Automated Grading System installation
    Locate the application directory and check for version identifiers in source files, README, or configuration. Common paths include /var/www/html or similar web root directories where the PHP application is hosted.
    Affected if The system is running SourceCodester CET Automated Grading System version 1.0 or another unpatched version of this software.
  2. Verify if the Student Self-Registration endpoint is accessible
    Test access to the registration functionality by attempting to reach the registration page via /index.php with registration-related parameters or paths. Check web server access logs for registration-related requests.
    Affected if The self-registration endpoint is publicly accessible without authentication requirements.
  3. Inspect access control logic in index.php and related files
    Examine the source code of index.php and any included files related to user registration. Look for authentication checks, session validation, or role verification before allowing self-registration actions.
    Affected if The code lacks proper authentication/authorization checks before permitting self-registration operations.
  4. Review user role and permission configuration
    Check the database or configuration files to determine how user roles are defined and whether any guest/unauthenticated users can be registered as students without admin approval.
    Affected if Unauthenticated users can self-register as students without proper role-based access control validation.

The environment is affected if it runs SourceCodester CET Automated Grading System 1.0 with the self-registration endpoint exposed and lacking proper authentication/authorization controls in index.php.

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 access control (RBAC) for the registration endpoint, including validation that users have appropriate permissions before allowing self-registration actions.

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-12529 — 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-12529 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