How exploitable is this vulnerability in a real deployment?

Exploitability is typically high if the /billaction.php endpoint is reachable by untrusted users and the database interaction uses concatenated SQL strings, because crafting malicious ID values requires no special tools or privileges.

Does an attacker need authenticated access to exploit this?

That depends on how the application is configured; if /billaction.php is accessible without authentication or with low-privilege accounts, an attacker only needs network access and the ability to send HTTP requests with a crafted ID parameter.

What is the safest general fix pattern for this issue?

The most robust pattern is to replace all dynamic SQL concatenation with prepared statements and bound parameters, combined with strict validation of the ID parameter and minimal database privileges for the web application user.

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) via ID Parameter in Vehicle Management System /billaction.php

CVE-2026-2867

Published:

Feb 21, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-74;CWE-89

Impact:

Data Exfiltration and Database Compromise

Severity:

HIGH RISK

(7.3)

CVSS Version:

3.1

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-74;CWE-89

Impact:

Data Exfiltration and Database Compromise

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.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

SQL Injection (CWE-89) via ID Parameter in Vehicle Management System /billaction.php

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare