CVE-2026-36722
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 · uneditedAn 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.
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 confidencebookcars v8.3 contains an authenticated arbitrary file upload vulnerability in the /api/create-car-image endpoint. An authenticated attacker can upload crafted files (e.g., malicious PHP scripts) to the server and execute arbitrary code by accessing the uploaded file.
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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
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.
-
Identify bookcars versionLocate the package.json file in the bookcars installation directory and check the 'version' field against v8.3 or compare to affected version rangeAffected if Installed version matches v8.3 or falls within the affected range
-
Verify /api/create-car-image endpoint existsCheck the backend source code for the presence of a route handler at /api/create-car-image, typically found in the routes or api folderAffected if The endpoint is defined and accessible in the application
-
Confirm endpoint requires authenticationExamine the route middleware for /api/create-car-image to determine if authentication middleware (such as authToken or similar) is appliedAffected if Authentication is enforced but file validation is missing or insufficient
-
Inspect file validation logicReview the file upload handler code within the create-car-image controller to identify what validation (if any) is performed on uploaded files (check for file type, extension, magic bytes)Affected if No file type validation, no extension allowlist, or no magic byte verification is implemented
-
Check upload storage configurationLocate where uploaded files are stored (typically an uploads or media directory) and determine if it is within the webroot and if script execution is permittedAffected if Uploads are stored in a web-accessible directory with script execution enabled
Your environment is affected if you are running bookcars v8.3 (or an affected version), the /api/create-car-image endpoint is exposed, and uploaded files are stored in a web-accessible location without proper validation.
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 strict file type validation (whitelist approach), rename uploaded files, store them outside the web root, and disable script execution in the upload directory. Additionally, require strong authentication for this endpoint and implement file content analysis rather than relying solely on file extension checks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36722 — 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-36722 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