CVE-2026-6164
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 security flaw has been discovered in code-projects Lost and Found Thing Management 1.0. This affects an unknown part of the file /addcat.php. Performing a manipulation of the argument cata results in sql injection. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks.
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 /addcat.php file of code-projects Lost and Found Thing Management 1.0, where the 'cata' parameter is not properly sanitized before being used in database queries, allowing remote attackers to inject malicious SQL commands.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 for files or metadata that identify it as 'Lost and Found Thing Management' version 1.0. Check application directories, README files, or version indicators.Affected if The application is code-projects Lost and Found Thing Management version 1.0
-
Locate the addcat.php fileSearch the web root directory for the file /addcat.php. This file handles category creation functionality in the application.Affected if The addcat.php file exists in the application directory and is accessible via the web server
-
Verify the cata parameter is processedExamine the addcat.php source code to confirm the 'cata' parameter is received and used in SQL queries without proper sanitization or parameterized queries.Affected if The 'cata' parameter is directly concatenated into SQL queries without escaping, binding, or sanitization functions
-
Confirm database connectivityVerify the application is configured with a database connection (MySQL/MariaDB typically) since SQL injection requires a database to exploit.Affected if The application has an active database connection and addcat.php executes SQL queries using user input from the cata parameter
-
Test for SQL injection presenceIf safe to do in a non-production environment, submit a harmless SQL payload in the cata parameter (e.g., single quote) and observe database error responses or behavior differences.Affected if Submitting special SQL characters in the cata parameter produces unexpected database errors or alters query behavior
You are affected if you are running Lost and Found Thing Management 1.0 with the addcat.php file accessible and the cata parameter is used in SQL queries without parameterized preparation.
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 the 'cata' parameter in addcat.php, and audit other files in the application for similar SQL injection vulnerabilities.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6164 — 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-6164 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