CVE-2023-5018
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 classified as critical has been found in SourceCodester Lost and Found Information System 1.0. This affects an unknown part of the file /classes/Master.php?f=save_category of the component POST Parameter Handler. The manipulation of the argument id leads to sql injection. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-239859.
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 confidenceSQL injection vulnerability in SourceCodester Lost and Found Information System 1.0 allows remote attackers to inject arbitrary SQL commands via the 'id' parameter in the POST request to /classes/Master.php?f=save_category. The application fails to properly sanitize user input before using it in SQL queries.
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.
-
Identify if Lost and Found Information System is deployedSearch the web server document root for files matching 'lost and found' or inspect the application banner/title via HTTP requests to the serverAffected if The application is present on the server and identifies as SourceCodester Lost And Found Information System
-
Confirm the application version is 1.0Inspect application files for a version identifier, typically in a README, version config, or footer file. Compare against the affected version = 1.0Affected if The installed version is exactly 1.0
-
Verify the vulnerable endpoint existsCheck for the existence of /classes/Master.php on the web server and confirm it accepts a 'save_category' function parameterAffected if The file /classes/Master.php?f=save_category is accessible and responds to POST requests
-
Inspect the save_category function for unsanitized input handlingExamine the PHP code in /classes/Master.php around the save_category function, specifically looking at how the 'id' parameter is handled in SQL queries without prepared statementsAffected if The code directly incorporates the 'id' parameter into SQL queries without using parameterized queries or input sanitization
-
Determine if the application is network-accessibleVerify whether the web server hosting the application accepts remote connections from untrusted networksAffected if The application is exposed to the internet or untrusted internal networks without network segmentation
A system is affected if it runs SourceCodester Lost And Found Information System version 1.0 with the /classes/Master.php endpoint accessible and the save_category function containing unsanitized SQL input handling for 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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for all user-controlled inputs, particularly the 'id' parameter in save_category. Additionally, implement input validation and output encoding as defense-in-depth measures.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5018 — 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-5018 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