dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-13568

HIGH · 7.3 CVSS v3.1 Published 2026-06-29
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 8 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 weakness has been identified in SourceCodester Inventory Management System 1.0. This vulnerability affects unknown code of the file /api/users_handler.php of the component User Registration Endpoint. This manipulation of the argument role causes improper access controls. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks.

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

This is a privilege escalation vulnerability in SourceCodester Inventory Management System 1.0's user registration endpoint (/api/users_handler.php). The 'role' parameter is not properly validated or authorized, allowing an attacker to manipulate this argument during registration to assign themselves elevated privileges (such as admin) beyond what the registration process should permit.

MitigationImplement server-side authorization checks to ensure users can only assign themselves roles they are explicitly authorized for, and validate the role parameter against a whitelist of permitted roles for the authenticated context.

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. Identify the installed version of SourceCodester Inventory Management System
    Locate the version information in the application source code, typically in a config file, README, or the main index page. Compare against version 1.0.
    Affected if The application version is 1.0 or cannot be determined to be a later patched version.
  2. Verify the vulnerable endpoint exists
    Check for the presence of the file /api/users_handler.php in the web application root directory.
    Affected if The file /api/users_handler.php exists and is accessible via HTTP.
  3. Determine if user registration is publicly accessible
    Examine the authentication requirements for the registration functionality. Check if the endpoint allows unauthenticated requests or if it can be accessed without a valid session or API key.
    Affected if The registration endpoint can be accessed without authentication or by any authenticated user.
  4. Inspect the role parameter handling in the code
    Review the source code of users_handler.php to see how the 'role' parameter is processed. Look for server-side validation or authorization checks on the role value before it is used.
    Affected if The code accepts a role parameter without validating it against an allowed list or checking user authorization to assign that role.
  5. Test if role parameter can be manipulated
    Send a registration request to /api/users_handler.php with an elevated role value (such as 'admin' or 'administrator') in the role parameter and observe if the user is created with that elevated role.
    Affected if A user can register with an elevated role beyond the default user role.

The environment is affected if running SourceCodester Inventory Management System version 1.0 with the /api/users_handler.php endpoint accessible and lacking proper server-side validation on the role parameter during user registration.

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 server-side authorization checks to ensure users can only assign themselves roles they are explicitly authorized for, and validate the role parameter against a whitelist of permitted roles for the authenticated context.

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