CVE-2023-33677 is a high severity (CVSS 7.5) unauthenticated SQL injection in Sourcecodester Lost and Found Information System version 1.0. An item view page passes an id parameter into a database query unsafely. No patched version is documented, so take it offline or fix the query code.
What's affected
- Sourcecodester Lost and Found Information System 1.0, listed in the record under the product name from the oretnom23 vendor entry.
- No fixed version appears in the NVD record or in the researcher notes we read.
- The flaw is reachable without logging in, according to the record.
The weakness is CWE-89, improper neutralization of special elements in an SQL command. The researcher notes list information disclosure as the impact.
How to check if you're exposed
This is a downloadable PHP and MySQL sample project, so there is no package manager check. Instead:
- Find out whether anyone in your organization deployed it. Search web server document roots for the project folder name and for the Sourcecodester download.
- Look at the version file or the original archive name to confirm you run version 1.0.
- Check web server access logs for unusual values in the id parameter of item view requests, such as quotes or SQL keywords.
If you find an instance that is reachable from the internet, treat it as exposed until you have fixed or removed it.
What to do now
- Take any internet-facing instance offline, or put it behind authentication at the web server or reverse proxy.
- Replace string-built queries in the item view code with prepared statements and bound parameters.
- Run the database account for the app with the least privilege it needs, and keep other applications on separate databases.
- Review logs and the database for signs that data was read, and notify the data owner if you find any.
- Decide whether the app is still needed. Sample projects often have no maintainer, so retirement may be the safer fix.
If you track software dependencies, the free in-browser dependency scan can show which of your components carry known CVEs, and the Gold directory lists the same records in one place.
Why it matters
SQL injection happens when user input becomes part of a query without being separated from the query structure. The database then treats attacker text as instructions. The record says the id value in the item view page is passed straight into a query.
The fix is well known and cheap in code: use parameterized queries. It is also a good reminder that free sample applications are code you now own. If nobody maintains the project upstream, a patch may never arrive, and your options are to patch it yourself or retire it.
The record shows this CVE is not in the CISA Known Exploited Vulnerabilities catalog, and the sources we read do not report exploitation in the wild.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is there a patched release?
None is documented in the record or the researcher notes we read. Check the vendor page for updates, and plan on fixing the query code yourself or removing the app.
Do I need to be logged in to be affected?
No. The record describes the issue as unauthenticated, which is why internet exposure is the first thing to check.
Sources
Last reviewed: 19 October 2026.