dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-5001

HIGH · 7.3 CVSS v3.1 Published 2026-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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
A flaw has been found in PromtEngineer localGPT up to 4d41c7d1713b16b216d8e062e51a5dd88b20b054. The affected element is the function do_POST of the file backend/server.py. This manipulation causes unrestricted upload. The attack is possible to be carried out remotely. The exploit has been published and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The vendor was contacted early about this disclosure but did not respond in any way.

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 upload vulnerability exists in the do_POST function of backend/server.py in PromtEngineer localGPT. The function lacks proper validation of uploaded file types, sizes, or content, allowing attackers to upload arbitrary files to the server. This vulnerability is remotely exploitable and has a public exploit available.

MitigationImplement strict file type validation (allowlist approach), enforce file size limits, validate file content/magic bytes, store uploads outside the web root with randomized filenames, and add proper access controls on uploaded files.

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
Low
Integrity
Low
Availability
Low

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

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. Confirm localGPT installation and version
    Locate the localGPT installation directory and check for version information in package metadata, setup files, or git tags. Common locations include the root directory of the localGPT repository.
    Affected if The installed version of localGPT matches or predates the version containing the vulnerable do_POST function in backend/server.py (compare your version against known fixed releases).
  2. Verify backend/server.py exists and is accessible
    Check for the presence of the file backend/server.py in the localGPT installation directory and confirm it contains a do_POST function that handles file uploads.
    Affected if The file backend/server.py exists with a do_POST function that processes file upload requests without proper validation.
  3. Check if the web server is configured to expose the file upload endpoint
    Review the web server configuration or API routes to identify if the do_POST function is exposed as a publicly accessible HTTP POST endpoint.
    Affected if The do_POST function is exposed via an HTTP endpoint that accepts file uploads without authentication or proper validation.
  4. Inspect file upload validation logic in do_POST
    Examine the source code of the do_POST function in backend/server.py to determine if file type, size, or content validation is implemented.
    Affected if The do_POST function lacks or has insufficient validation for file types, sizes, or content (magic bytes) before saving uploaded files.
  5. Check the web root and upload directory configuration
    Determine where uploaded files are stored relative to the web root. Inspect any configuration for upload paths.
    Affected if Uploaded files are stored within the web root or in a location accessible via the web server without access controls.

You are affected if localGPT with the vulnerable do_POST function in backend/server.py is installed and the file upload endpoint is exposed without proper validation controls.

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 file type validation (allowlist approach), enforce file size limits, validate file content/magic bytes, store uploads outside the web root with randomized filenames, and add proper access controls on uploaded files.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5001 — 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-5001 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