/

CVE-2026-85516

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Vehicle Management System

CVE-2026-85516

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise and unauthorized data access

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity SQL injection vulnerability in the Vehicle Management System may allow attackers to manipulate database queries through the busid parameter in /busprofile.php.

Because the affected function is remotely reachable, an attacker may be able to access, alter, or interfere with database information without needing local system access.

Affected context

The vulnerability occurs in Vehicle Management System 1.0 when the remotely accessible /busprofile.php endpoint incorporates the busid request parameter into database operations without sufficiently separating user-controlled data from SQL commands. Deployments are at greater risk when this endpoint is exposed to untrusted networks and database permissions are broader than required.

Exploit preconditions

  • Attack surface: Remotely accessible web endpoint
  • Required access: Ability to send requests to /busprofile.php; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the busid parameter
  • Why exploitation is possible: User-controlled input may influence SQL statement construction without adequate parameterization or validation

Why this happens

The underlying bug is an injection flaw in which externally supplied input is interpreted as part of a database query rather than strictly as data. This behavior maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and is also related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component. The insecure pattern typically involves dynamically assembling SQL statements with untrusted request parameters.

Potential impact

  • An attacker may read sensitive records from the application database.
  • An attacker could modify or delete vehicle-management data.
  • The vulnerability may enable authentication or authorization data exposure.
  • Database availability could be reduced through disruptive queries.
  • Compromised data could affect operational decisions or downstream systems.

General mitigation guidance

Mitigation generally focuses on ensuring that all database access treats request data as values rather than executable query syntax.

Common defensive patterns include:

  • Using parameterized queries or prepared statements by default
  • Applying allowlist validation for identifiers such as numeric record IDs
  • Avoiding dynamic SQL construction where a fixed query structure is sufficient
  • Limiting database accounts to the minimum required operations and data
  • Separating application and administrative database privileges
  • Returning generic error messages without exposing query details
  • Restricting unnecessary public access to administrative or record-management endpoints

How teams detect issues like this

Detection approaches commonly include:

  • Static analysis rules that identify string concatenation or interpolation in SQL execution paths
  • Code review checks for request parameters passed directly into database APIs
  • Dynamic application testing for unexpected database errors and input-handling anomalies
  • Web application firewall policies focused on suspicious database-oriented request patterns
  • Database monitoring for unusual query structures, access volumes, or privilege use
  • Automated security review tools that flag missing parameterization and weak input validation

Sources

SourceLink
code-projects.orgcode-projects.org/
github.comgithub.com/ahmadmarz10-hub/CVEsMarz/blob/main/SQL%20Injection%20Vulnerability%20in%20Vehicle%20Management%20System%20%60busid%60%20Parameter.md
vuldb.comvuldb.com/cve/CVE-2026-85516
vuldb.comvuldb.com/submit/895112
vuldb.comvuldb.com/vuln/398680
vuldb.comvuldb.com/vuln/398680/cti

Frequently asked

questions

Yes. The affected web functionality is remotely reachable, although actual exposure depends on network access controls and any authentication required by the deployment.

An attacker needs the ability to submit requests to the affected endpoint and influence the busid parameter. Whether a valid account is required depends on how the application is configured.

Use parameterized queries or prepared statements for database operations, combined with strict validation appropriate to the expected busid format.

Enforce secure database-access patterns in shared libraries and code review, apply least-privilege database permissions, test request parameters at application boundaries, and monitor for anomalous query activity.

Find out what's already
exploitable in your codebase.