CVE-2026-7404
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 · uneditedA weakness has been identified in getsimpletool mcpo-simple-server up to 0.2.0. Affected is the function delete_shared_prompt of the file src/mcpo_simple_server/services/prompt_manager/base_manager.py. This manipulation of the argument detail causes relative path traversal. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
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 confidenceA path traversal vulnerability exists in the delete_shared_prompt function of mcpo-simple-server up to v0.2.0. The function fails to sanitize the 'detail' argument, allowing attackers to manipulate relative path sequences (e.g., ../../../) to access or delete files outside the intended directory. This is remotely exploitable and the exploit is publicly available.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify mcpo-simple-server installationSearch for mcpo-simple-server processes running on the system, or locate the installation directory using commands like 'ps aux | grep mcpo' or by finding the application binary/package.Affected if mcpo-simple-server is installed and running
-
Determine installed versionRun 'mcpo-simple-server --version' or check the package manifest (package.json, setup.py, or similar) to obtain the exact version number, then compare to the affected range (up to v0.2.0).Affected if Version is 0.2.0 or lower
-
Verify delete_shared_prompt endpoint is exposedReview API documentation or network exposure configuration to confirm the delete_shared_prompt function is accessible via HTTP/HTTPS API endpoints.Affected if The delete_shared_prompt API endpoint is reachable over the network
-
Inspect request handling for detail parameterExamine application logs or HTTP access logs for requests to the delete_shared_prompt endpoint containing path traversal sequences like '../' in the 'detail' parameter.Affected if Suspicious requests with '../' sequences in the detail parameter are found in logs
-
Check for unauthorized file deletionsReview file system changes or application audit logs to detect if files outside the intended prompts directory have been modified or deleted.Affected if Files outside the expected prompts directory have been deleted or modified
A user is affected if mcpo-simple-server version 0.2.0 or lower is running with the delete_shared_prompt endpoint exposed, and the 'detail' parameter is not validated to prevent path traversal.
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 input validation on the 'detail' parameter to reject path traversal sequences; validate that the resolved path remains within the expected directory. Until a vendor patch is released, restrict network access to the affected service and monitor for exploitation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7404 — 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-7404 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