Quick answers
- Is CVE-2026-36722 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-36722 being exploited in the wild.
- How severe is CVE-2026-36722?
- Informational severity, with a CVSS score of 6.5, published 9 June 2026.
- Which products and versions are affected?
- BookCars <= 8.3.
- Is there a fix for CVE-2026-36722?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-36722 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-36722?
- Check whether you run BookCars at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An unrestricted file upload vulnerability exists in BookCars <= v8.3 within the /api/create-license and /api/create-car-image endpoints. The root cause is a lack of file extension validation and content verification in the userController.ts and carController.ts components; the application merely generates a unique filename using nanoid() and preserves the original extension. An authenticated attacker can upload malicious files (such as .html for XSS or potentially server-side executable scripts depending on the environment) to the CDN temporary directory. While the NVD description suggests arbitrary code execution, the technical PoC demonstrates stored Cross-Site Scripting (XSS) by uploading HTML files containing JavaScript. Remediation requires implementing a strict whitelist of allowed extensions and verifying file headers (magic bytes).
Affected products
- BookCars BookCars <= 8.3
Timeline
- 2026-06-09: disclosed: CVE-2026-36722 published