CVE-2026-5196
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 has been found in code-projects Student Membership System 1.0. Impacted is an unknown function of the file /delete_member.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated 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 · moderate confidenceSQL injection vulnerability in the /delete_member.php file of Student Membership System 1.0 allows remote attackers to manipulate SQL queries via the unsanitized ID parameter. This could enable unauthorized data deletion, database exposure, or potentially remote code execution depending on database configuration.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed applicationLocate the web application on the server and check its name/version. Look for identifying files such as README, index.php header, or admin panels that display the application name. For Student Membership System, check common web directories for a folder containing 'student' or 'membership' related files.Affected if The application is Student Membership System version 1.0
-
Verify delete_member.php existsCheck the web server's document root for the presence of /delete_member.php or a path containing delete_member.php. This file is part of the admin/user management functionality of the application.Affected if The file delete_member.php exists in the web application directory
-
Inspect the ID parameter handling in the codeOpen delete_member.php in a text editor and locate the SQL query that uses the ID parameter. Examine whether the ID parameter is directly inserted into the SQL query string without using prepared statements, parameterized queries, or input sanitization functions such as htmlspecialchars, mysqli_real_escape_string, or PDO binding.Affected if The ID parameter is concatenated directly into the SQL query without sanitization or parameterization
-
Test for SQL injection susceptibilityIf the endpoint is accessible, send a request to delete_member.php with a crafted ID value such as "1' OR '1'='1" or "1; DELETE FROM members--" and observe whether the application returns unexpected results, database errors, or behaves differently than expected.Affected if The application returns database error messages or exhibits unexpected behavior indicating the SQL query was modified by the injected input
-
Check database user privilegesReview the database configuration file (commonly config.php, db.php, or similar in the application root) to determine the privilege level of the database user connected to the application. Look for whether the database user has DROP, DELETE, or administrative privileges beyond what the application requires.Affected if The database user has elevated privileges (DROP, DELETE, or administrative rights) that could be exploited through SQL injection
You are affected if Student Membership System 1.0 is deployed, delete_member.php exists, and the ID parameter is used in SQL queries without prepared statements or input sanitization.
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.
dbcve · scopedReplace dynamic SQL queries with parameterized queries/prepared statements in delete_member.php and validate/sanitize all user inputs. Apply principle of least privilege to database accounts.
- This vulnerability is in a third-party PHP application from code-projects.org that does not appear to have an official vendor patch or structured release cycle.
- To remediate SQL injection in /delete_member.php, manually apply parameterized queries (PDO prepared statements) instead of concatenating the ID parameter directly into SQL.
- Replace direct SQL queries like "DELETE FROM members WHERE ID='$id'" with prepared statements such as "$stmt = $pdo->prepare('DELETE FROM members WHERE ID = :id'); $stmt->execute(['id' => $id]);"
- Ensure input validation is performed on the ID parameter (e.g., ensure it is numeric using is_numeric() or intval()) before using it in queries.
- Apply the principle of least privilege to the database user - the application should only have permissions necessary for its operations.
- After applying fixes, conduct penetration testing to verify the SQL injection is eliminated.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5196 — 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-5196 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