CVE-2023-0981
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 Yoga Class Registration System 1.0. It has been classified as critical. Affected is an unknown function of the component Delete User. The manipulation of the argument id leads to sql injection. It is possible to launch the attack remotely. The identifier of this vulnerability is VDB-221676.
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 User function of SourceCodester Yoga Class Registration System 1.0 allows remote attackers to manipulate SQL queries through the unprotected 'id' parameter, potentially enabling unauthorized data access, modification, or deletion.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Yoga Class Registration System installationLocate the application files - typically deployed in a web server document root (e.g., htdocs, www, or public_html). Look for files named 'delete_user.php' or similar in the user management section of the application.Affected if The application directory contains SourceCodester Yoga Class Registration System files, particularly any file handling user deletion.
-
Identify the Delete User functionSearch the application source code for functions or files handling user deletion. Look for PHP files containing 'delete', 'user', or 'id' parameter handling in SQL queries.Affected if A Delete User function exists and processes an 'id' parameter without proper input handling.
-
Examine SQL query construction in Delete User codeOpen the identified delete user file and inspect the database query code. Look for SQL statements (SELECT, DELETE, UPDATE) that directly incorporate the 'id' parameter into the query string.Affected if The 'id' parameter is concatenated directly into SQL queries without prepared statements, parameter binding, or type casting.
-
Verify input validation on the id parameterReview the code preceding the SQL query to check if the 'id' parameter undergoes any validation such as type checking (is_numeric, intval), allowlist validation, or sanitization functions before being used in the query.Affected if No input validation exists, or validation can be bypassed, allowing arbitrary SQL syntax in the 'id' parameter.
-
Test Delete User endpoint for SQL injectionIf the application is accessible, use a browser or HTTP tool to send a request to the Delete User endpoint with a test payload in the 'id' parameter, such as '1' OR '1'='1', and observe if unexpected data behavior occurs or if the application returns a database error.Affected if The application executes the injected SQL syntax or returns SQL error messages indicating unsanitized input is being processed.
The environment is affected if Yoga Class Registration System 1.0 is running and the Delete User function directly incorporates the 'id' parameter into SQL queries without prepared statements or proper input validation.
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 prepared statements/parameterized queries for all database operations, especially in the Delete User function. Validate and sanitize the 'id' parameter using allowlist validation for numeric/integer types.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0981 — 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-2023-0981 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