CVE-2025-8376: A vulnerability classified as critical has been found in code-projects Vehicle Management 1.0

This week

HIGH 7.3REMOTEDOWNGRADE

CVE-2025-8376 is a high-severity flaw (CVSS 7.3) affecting vehicle management. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability classified as critical has been found in code-projects Vehicle Management 1.0. Affected is an unknown function of the file /updatebal.php. The manipulation of the argument company leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-74, CWE-89
Published	2025-07-31
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: code-projects

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-07-31 10:15 UTCPublished CVE record published
2026-06-17 10:06 UTCUpdated Record last modified

code-projects vehicle management DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy vehicle-management || rpm -q vehicle-management || vehicle-management --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison vehicle-management sudo apt install vehicle-management=<VERSION_BEFORE_1.0> sudo apt-mark hold vehicle-management

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vehicle-management sudo dnf downgrade vehicle-management-<VERSION_BEFORE_1.0> sudo dnf versionlock add vehicle-management

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-8376?

vehicle management: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-8376 being exploited?

CVE-2025-8376 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-8376 affect?

CVE-2025-8376 affects vehicle management. Severity is high (CVSS 7.3). A vulnerability classified as critical has been found in code-projects Vehicle Management 1.0. Affected is an unknown function of the file /updatebal.php. The manipulation of the argument company leads to sql injection. It is possible to la

How urgent is CVE-2025-8376?

Priority 48/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

CVE-2025-8409 HIGH 7.3 DOWNGRADE A vulnerability has been found in code-projects Vehicle Management 1.0 and classified as critical
CVE-2025-8408 HIGH 7.3 DOWNGRADE A vulnerability, which was classified as critical, was found in code-projects Vehicle Management 1.0
CVE-2025-8407 HIGH 7.3 DOWNGRADE A vulnerability, which was classified as critical, has been found in code-projects Vehicle Management 1.0
CVE-2025-8375 HIGH 7.3 DOWNGRADE A vulnerability was found in code-projects Vehicle Management 1.0
CVE-2025-8374 HIGH 7.3 DOWNGRADE A vulnerability was found in code-projects Vehicle Management 1.0

References

← Back to latest CVEs