CVE-2026-5326
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 · uneditedA vulnerability was identified in SourceCodester Leave Application System 1.0. Impacted is an unknown function of the file /index.php?page=manage_user of the component User Information Handler. Such manipulation of the argument ID leads to authorization bypass. The attack can be executed remotely. The exploit is publicly available and might be used.
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 confidenceAn authorization bypass vulnerability exists in SourceCodester Leave Application System 1.0 within the User Information Handler functionality at /index.php?page=manage_user. The ID parameter is not properly validated, allowing attackers to manipulate it to access or modify user information without proper authorization. The attack can be exploited remotely and a public exploit exists.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SourceCodester Leave Application System is installedSearch for the application files in your web root directory. Look for directories containing 'leave' or 'leave_application' or check for the presence of index.php with leave system branding.Affected if The application is present in the environment.
-
Identify the installed versionCheck for a version file, about page, or footer in the application. Common locations include a /about, /info endpoint or the footer of the main page. Compare the version to 1.0.Affected if The installed version is 1.0.
-
Verify the manage_user endpoint existsAttempt to access /index.php?page=manage_user or check if the file manage_user.php exists in the web application directory.Affected if The manage_user functionality is present and accessible.
-
Check if authentication is required for the vulnerable pageAttempt to access the manage_user page without logging in (clear cookies/session and visit the URL). Verify whether the application redirects to a login page or allows anonymous access.Affected if The page is accessible without authentication or without proper session validation.
-
Inspect the ID parameter authorization logicExamine the source code of the manage_user handler (typically in a users.php, user.php, or handler file). Look for code that validates the user ID against the authenticated user's permissions before performing actions.Affected if The code lacks proper authorization checks on the ID parameter before allowing access or modification of user data.
A user is affected if they have SourceCodester Leave Application System version 1.0 running with the manage_user functionality accessible and lacking proper authorization validation on the ID parameter.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks on all user management operations, validate that the authenticated user has permission to access or modify the requested user ID, and enforce role-based access controls before performing any action on the ID parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-5326 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5326 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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