CVE-2026-10170
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 flaw has been found in code-projects Visitor Management System 1.0. Affected by this issue is some unknown functionality of the file /vms/php/phone_0.php. This manipulation of the argument phone causes sql injection. The attack may be initiated remotely. The exploit has been published and may be used.
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 code-projects Visitor Management System 1.0's /vms/php/phone_0.php file. The 'phone' parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Visitor Management System installationSearch the web server for files or directories named 'vms' or 'visitor management system'. Check for the presence of the /vms/php/ directory structure.Affected if The Visitor Management System 1.0 application is installed on the server.
-
Locate the vulnerable phone_0.php fileSearch for the file /vms/php/phone_0.php in the web root directory. This is the specific file containing the SQL injection vulnerability.Affected if The file /vms/php/phone_0.php exists on the system.
-
Inspect the phone_0.php code for unsanitized SQLOpen phone_0.php and examine how the 'phone' parameter is handled. Look for SQL queries that incorporate the phone parameter directly without using prepared statements, parameter binding, or input sanitization functions.Affected if The code contains dynamic SQL queries using the phone parameter without prepared statements or input validation.
-
Verify the phone parameter is exposedAccess the phone_0.php endpoint via HTTP GET or POST and confirm the 'phone' parameter is accepted. The vulnerability is exploitable when user-supplied phone input reaches the database query.Affected if The phone parameter is accepted and processed by phone_0.php without sanitization.
-
Check for SQL injection evidenceSubmit a test payload such as ' OR '1'='1 in the phone parameter and observe database behavior or error messages. Review database query logs for unexpected SQL syntax.Affected if The application returns database errors or executes SQL commands based on injected input.
The system is affected if Visitor Management System 1.0 is installed and the /vms/php/phone_0.php file exists with the phone parameter handling vulnerable to SQL injection.
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 in phone_0.php. Validate and sanitize all user inputs before using them in database queries.
- Consultation4.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10170 — 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-10170 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