What is the CVSS score of CVE-2026-36722?

CVE-2026-36722 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

bookcars CVE-2026-36722

MEDIUM

Unrestricted Upload of File with Dangerous Type (CWE-434)

2026-06-09 mitre

RCE File Upload N A

5.4

CVSS 3.1 · Vendor: mitre

Severity by source

Vendor (mitre) PRIMARY

5.4 MEDIUM

AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Primary rating from Vendor (mitre) · only source for this CVE.

CVSS VectorVendor: mitre

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 10, 2026 - 18:22 vuln.today

CVSS changed

Jun 10, 2026 - 18:22 NVD

5.4 (MEDIUM)

CVE Published

Jun 09, 2026 - 00:00 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

An authenticated arbitrary file upload vulnerability in the /api/create-car-image component of bookcars v8.3 allows attackers to execute arbitrary code via uploading a crafted file.

AnalysisAI

Arbitrary file upload via the /api/create-car-image endpoint in bookcars v8.3 enables server-side code execution by uploading a crafted file (e.g., a web shell). The vulnerability targets an image upload API that fails to restrict file types per CWE-434. No public exploit identified at time of analysis, and EPSS sits at 0.02% (6th percentile), indicating negligible observed exploitation pressure - however, two data conflicts significantly affect confidence: the description asserts an authenticated attacker is required while the CVSS vector records PR:N (no privileges required), and the CVSS impact scores of C:L/I:L are inconsistent with the claimed remote code execution outcome.

Technical ContextAI

bookcars is an open-source car rental platform. The vulnerable component is the /api/create-car-image API endpoint, which accepts file uploads for vehicle images. CWE-434 (Unrestricted Upload of File with Dangerous Type) describes server-side endpoints that accept user-supplied files without validating content type, extension, or magic bytes against an allowlist of safe formats. If the upload directory is web-accessible and the server interprets server-side scripts (e.g., PHP), an attacker can upload a script disguised as an image and trigger execution via a direct HTTP request to the stored file. The CPE entry is listed as cpe:2.3:a:n/a:n/a, meaning NVD has not assigned a normalized CPE identifier for bookcars v8.3, which limits automated scanner detection.

RemediationAI

No vendor-released patch has been identified at time of analysis. The primary remediation is to implement strict server-side file type validation on the /api/create-car-image endpoint: validate file extensions against an allowlist (e.g., .jpg, .png, .webp only), inspect file magic bytes independent of extension, and reject any file whose MIME type does not match an allowed image format. Store uploaded files outside the web root or in a dedicated object storage bucket (e.g., S3) to prevent direct HTTP execution of uploaded scripts - this is the most impactful compensating control since it breaks the execution step even if upload succeeds. Additionally, rename uploaded files to randomized UUIDs with enforced extensions to prevent predictable access. If the upload feature is non-essential, consider disabling the /api/create-car-image endpoint at the application or reverse proxy layer until a patch is available. The community disclosure is available at https://github.com/CC-T-454455/Vulnerabilities/tree/master/bookcars/vulnerability-16 and should be monitored for patch announcements.