CVE-2026-5330
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 found in SourceCodester/mayuri_k Best Courier Management System 1.0. Affected by this issue is some unknown functionality of the file /ajax.php?action=delete_user of the component User Delete Handler. Performing a manipulation of the argument ID results in improper access controls. The attack may be initiated remotely. The exploit has been made public and could 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 confidenceThis is an IDOR (Insecure Direct Object Reference) vulnerability in the Best Courier Management System 1.0 where the /ajax.php?action=delete_user endpoint lacks proper authorization checks. An attacker can manipulate the ID parameter to delete arbitrary users without being authenticated or without proper permissions, leading to unauthorized data modification.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Best Courier Management System is installedInspect your web server's document root for a folder containing 'courier' or 'Best Courier Management System' related files. Check for the presence of ajax.php in the application root directory.Affected if The application folder and ajax.php file exist and the application is Best Courier Management System version 1.0
-
Verify the application versionCheck for a version file, README, or changelog in the application root. Common locations include version.php, README.txt, or the footer of admin login pages.Affected if The installed version is 1.0 or cannot be determined (assume affected if unknown)
-
Locate the vulnerable endpointSearch for the file ajax.php in the application root. Within that file, locate the code block handling 'delete_user' action.Affected if The file ajax.php exists and contains a case or handler for the 'delete_user' action
-
Inspect authorization logic on delete_userOpen ajax.php and examine the code around the delete_user handler. Look for session validation, role checks, or permission verification before executing the delete operation.Affected if No session checks, no user role verification, or no ownership validation is performed before deleting the user
-
Check if the endpoint is accessible without authenticationReview the ajax.php file for any authentication includes or checks at the top of the file. Verify if the delete_user function is wrapped in a gate that requires a logged-in session.Affected if The delete_user endpoint can be reached without a valid session or authentication token
If Best Courier Management System version 1.0 is installed and the delete_user endpoint in ajax.php lacks proper session validation and authorization checks before processing user deletion, the environment is affected by CVE-2026-5330.
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 to verify the requesting user has permission to delete the target user, along with authentication validation. Consider adding CSRF tokens for state-changing operations.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5330 — 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-5330 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