dbcve.org
Lost And Found Information SystemApplication · Oretnom23

CVE-2023-3679

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-15
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
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 was found in SourceCodester Lost and Found Information System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /classes/Master.php?f=save_inquiry of the component HTTP POST Request Handler. The manipulation of the argument id leads to sql injection. The attack may be launched remotely. The identifier of this vulnerability is VDB-234224.

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

SQL injection vulnerability in SourceCodester Lost and Found Information System 1.0 allows remote attackers to inject malicious SQL queries via the 'id' parameter in the /classes/Master.php?f=save_inquiry POST request handler. The application fails to properly sanitize user input before using it in SQL queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in the save_inquiry function of Master.php. Validate and sanitize all user inputs before database operations.

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
Lost And Found Information SystemApplication
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. Confirm Lost and Found Information System is installed
    Check your web server document root for the presence of the Lost and Found Information System application. Look for directories containing files like index.php, Master.php, or similar application files.
    Affected if The application directory is present on the server.
  2. Identify the installed version
    Check for a version file, readme file, or examine the main index.php for a version string. Also check the source code comments or any config files that may indicate version 1.0.
    Affected if The installed version is Oretnom23 Lost And Found Information System version 1.0.
  3. Locate the vulnerable Master.php file
    Navigate to the /classes/ directory in the application root and locate Master.php. Verify the file exists and contains a function named save_inquiry.
    Affected if The file /classes/Master.php with the save_inquiry function exists in the application.
  4. Inspect the save_inquiry function for SQL injection vulnerability
    Open Master.php and locate the save_inquiry function. Examine the SQL query construction within this function, specifically looking for direct use of the 'id' parameter in SQL statements without prepared statements or parameter binding.
    Affected if The code uses the 'id' parameter directly in SQL queries without sanitization or parameterized queries.
  5. Verify the vulnerable endpoint is accessible
    Confirm the application web interface is accessible and the endpoint /classes/Master.php?f=save_inquiry is reachable via POST requests.
    Affected if The application is running and accessible over the network with the vulnerable endpoint available.

If the system runs Oretnom23 Lost And Found Information System version 1.0 with the vulnerable Master.php file containing unsanitized 'id' parameter usage in the save_inquiry function, the environment is affected by this SQL injection vulnerability.

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

Replace dynamic SQL queries with parameterized queries/prepared statements in the save_inquiry function of Master.php. Validate and sanitize all user inputs before database operations.

Fix this in Lost And Found Information System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3679 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-3679 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