Simple Car Rental SystemApplication · Fabian

CVE-2025-7476

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability classified as critical was found in code-projects Simple Car Rental System 1.0. This vulnerability affects unknown code of the file /admin/approve.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public 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 · high confidence

SQL injection vulnerability in Simple Car Rental System 1.0's /admin/approve.php script allows remote attackers to manipulate the ID parameter to inject arbitrary SQL queries. The critical CVSS score of 9.8 reflects the ease of exploitation and potential for complete database compromise.

MitigationReplace dynamic SQL queries in /admin/approve.php with prepared statements or parameterized queries, ensuring the ID parameter is properly escaped and validated before database execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Simple Car Rental SystemApplication
Affected:= 1.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Simple Car Rental System installation
    Locate the web application directory and identify if it contains the Simple Car Rental System codebase. Check for known files such as index.php, admin/login.php, or configuration files that reference the application name.
    Affected if The application directory contains Simple Car Rental System files.
  2. Verify approve.php exists
    Check for the presence of the file /admin/approve.php in the web root directory.
    Affected if The file /admin/approve.php exists in the application.
  3. Identify installed version
    Review version information in source files such as README, changelog, version.php, or the admin dashboard footer. Compare the installed version to the affected range: version 1.0.
    Affected if The installed version is exactly 1.0.
  4. Assess network accessibility
    Determine if the /admin/approve.php endpoint is reachable from the network. Check web server configuration and firewall rules to confirm external or unauthorized access is possible.
    Affected if The /admin/approve.php endpoint is accessible over the network to unauthorized users.
  5. Review ID parameter handling in approve.php
    Examine the source code of /admin/approve.php and locate the SQL query that uses the ID parameter. Check whether the ID value is used directly in the query string or passed through parameterized queries (prepared statements).
    Affected if The ID parameter is concatenated directly into SQL queries without using prepared statements or input sanitization.

You are affected if Simple Car Rental System version 1.0 is installed, the /admin/approve.php file exists, and the ID parameter in that file is used in SQL queries without parameterized queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries in /admin/approve.php with prepared statements or parameterized queries, ensuring the ID parameter is properly escaped and validated before database execution.

Fix this in Simple Car Rental System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7476 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7476 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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