CVE-2026-37345
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 · uneditedSourceCodester Vehicle Parking Area Management System v1.0 is vulnerable to SQL Injection in the file /parking/manage_park.php.
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 SourceCodester Vehicle Parking Area Management System v1.0 allows attackers to inject malicious SQL queries via unspecified parameters in /parking/manage_park.php. The critical CVSS score of 9.8 indicates potential for complete compromise of the database, including exfiltration of sensitive data or administrative access.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the application is installedLocate SourceCodester Vehicle Parking Area Management System on the server by checking web root directories for parking management related files or folders.Affected if The application is present on the server.
-
Verify the file manage_park.php existsCheck for the presence of /parking/manage_park.php in the web application's directory structure.Affected if The file /parking/manage_park.php exists in the installation.
-
Identify installed versionCheck version.php, readme.txt, or any version metadata file in the application root for version 1.0, or examine the manage_park.php file header for version information.Affected if The installed version is 1.0.
-
Inspect SQL query handling in manage_park.phpOpen /parking/manage_park.php and search for SQL query execution functions (mysqli_query, mysql_query, PDO query, etc.) that use direct string concatenation with user-supplied parameters (such as $_GET, $_POST, $_REQUEST).Affected if Dynamic SQL queries concatenate user input directly without prepared statements or parameter binding.
-
Check if user input reaches the vulnerable codeReview the manage_park.php file to identify which parameters (POST/GET) are accepted and trace whether they flow into unsanitized SQL queries.Affected if User-supplied parameters from HTTP requests are used in SQL queries without sanitization.
If the SourceCodester Vehicle Parking Area Management System v1.0 is installed with the file /parking/manage_park.php present and that file uses dynamic SQL with unsanitized user input, the environment is affected by this CVE.
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 dataImplement parameterized queries or prepared statements for all database interactions in manage_park.php and conduct a comprehensive code review to identify and remediate additional SQL injection points across the application.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37345 — 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-37345 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