dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-36723

HIGH · 8.8 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An unrestricted file rename vulnerability in the /api/create-user component of bookcars v8.3 allows authenticated attackers to leverage directory traversal sequences to move arbitrary files from temporary storage to arbitrary locations on the server filesystem. This enables unauthorized access to sensitive files, the overwriting of critical application files, and remote code execution (RCE).

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 confidence

An unrestricted file rename vulnerability in the /api/create-user endpoint of bookcars v8.3 allows authenticated attackers to use directory traversal sequences (e.g., ../../../) to move files from temporary storage to arbitrary filesystem locations, enabling unauthorized access to sensitive files, critical file overwriting, and potential remote code execution.

MitigationImplement strict path validation to deny directory traversal sequences (../), restrict file operations to allowed directories only, and validate user permissions before performing any file move operations in the create-user endpoint.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify the installed bookcars version
    Locate the package.json file in the bookcars installation directory and read the version field, or run 'npm list bookcars' if installed as a Node.js module
    Affected if The installed version is 8.3 or falls within the affected range around v8.3
  2. Verify the /api/create-user endpoint exists
    Check the application routes or source code for the presence of a route handler at /api/create-user in the API routing configuration
    Affected if The endpoint exists and is defined in the application's route files
  3. Confirm authentication is enforced on the endpoint
    Inspect the middleware stack for /api/create-user in the route definition to verify that an authentication middleware (such as a session check or JWT validator) is applied before the route handler
    Affected if No authentication middleware is attached to the /api/create-user route, or authentication can be bypassed
  4. Check for directory traversal validation in the rename logic
    Review the file rename implementation within the create-user controller, looking for path sanitization that prevents or allows traversal sequences like ../ in the destination path parameter
    Affected if The code accepts user-controlled path parameters without validating that the destination remains within an allowed directory
  5. Inspect temporary file storage permissions
    Locate the temporary storage directory used during user creation (commonly a temp or uploads folder) and verify file permissions allow the application process to move files from this location
    Affected if The application process has write access to directories outside the intended temp scope, enabling the traversal attack to place files in web-accessible locations

A defender is affected if running bookcars v8.3 (or the relevant version range), the /api/create-user endpoint is exposed, authentication is missing or bypassable, and the application lacks directory traversal validation on file rename operations.

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

Implement strict path validation to deny directory traversal sequences (../), restrict file operations to allowed directories only, and validate user permissions before performing any file move operations in the create-user endpoint.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-36723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2026-36723 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