Client Database Management SystemDatabase / datastore · Lerouxyxchire

CVE-2026-3762

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 vulnerability has been found in SourceCodester Client Database Management System 1.0/3.1. Impacted is an unknown function of the file /superadmin_delete_manager.php of the component Endpoint. The manipulation of the argument manager_id leads to improper authorization. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may 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 · high confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in the /superadmin_delete_manager.php endpoint. The manager_id parameter can be manipulated by remote attackers to delete arbitrary manager accounts without proper authorization checks.

MitigationImplement proper session-based authorization checks to verify the authenticated user has permission to delete the specific manager account before executing the deletion operation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Client Database Management SystemDatabase / datastore
Affected:= 1.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installed product and version
    Locate the Lerouxyxchire Client Database Management System installation and determine its version number. Check application metadata, about page, or installation files for version 1.0.
    Affected if The installed version is Lerouxyxchire Client Database Management System version 1.0
  2. Verify endpoint presence
    Check if the file /superadmin_delete_manager.php exists in the web application directory structure.
    Affected if The endpoint /superadmin_delete_manager.php is present on the server
  3. Inspect authorization logic
    Review the source code of superadmin_delete_manager.php to determine if session-based authorization checks are performed before executing the deletion. Look for session validation and permission verification logic around the manager_id parameter handling.
    Affected if No session-based authorization check exists before processing the manager_id parameter, or the manager_id is used directly in the delete query without verifying the current user has permission to delete that specific manager
  4. Test parameter manipulation
    With an authenticated low-privilege session, attempt to send a request to /superadmin_delete_manager.php with a manager_id value different from your own to see if you can delete another manager account.
    Affected if A user can delete manager accounts other than their own without receiving an authorization error

A user is affected if they run Lerouxyxchire Client Database Management System version 1.0 with the /superadmin_delete_manager.php endpoint present and accessible without proper authorization controls on the manager_id parameter.

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 session-based authorization checks to verify the authenticated user has permission to delete the specific manager account before executing the deletion operation.

Fix this in Client Database Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3762 — 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-3762 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