---
id: "CVE-2026-114519"
kind: "vulnerability"
aliases: ["CVE-2026-114519"]
title: "Prospero Flow CRM: any basic user can read and delete other accounts"
severity: "high"
cvss: 8.6
epss: 0.00357
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["other", "prospero-flow-crm", "self-hosted"]
not_affected_if: ["version-5.26.0-or-later", "version-before-2.0.0"]
published_at: "2026-10-22T19:17:37+00:00"
first_seen_at: "2026-10-23T21:57:31+00:00"
updated_at: "2026-10-24T07:15:51+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114519", "first_seen_at": "2026-10-23T21:57:31+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-114519", "first_seen_at": "2026-10-24T07:15:51+00:00"}]
---

# Prospero Flow CRM: any basic user can read and delete other accounts

Roskus Prospero Flow CRM versions 2.0.0 before 5.26.0 let a basic-role user read other users' accounts in their company, including higher-privilege accounts, with email, phone, postal address and IBAN exposed. From version 3.5.0, the same flaw lets that user delete accounts, including the last admin of a company, and in the default company it can delete accounts across all companies.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

Check the installed Prospero Flow CRM version; versions 2.0.0 up to but not including 5.26.0 are affected.

## Fix

Upgrade Prospero Flow CRM to version 5.26.0 or later.

## Timeline

- 2026-10-23T21:57:31+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-114519
- 2026-10-24T07:15:51+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-114519

## From the sources

Missing Authorization (CWE-862) in the user API of Roskus Prospero Flow CRM from 2.0.0 before 5.26.0 allows a user with a basic role to read the accounts of other users of its own company, including accounts with higher privileges, and, in versions from 3.5.0, to delete them, because the routes GET /api/user/{id} and DELETE /api/user/{id} in routes/api.php carry only the auth:api middleware, which checks that a JSON Web Token is valid and nothing more, and neither UserReadController::read() nor UserDeleteController::delete() checks a permission, a policy or a role before acting. Object access is scoped by company: the read path limits the query to the company of the authenticated user, and the delete path compares the company of the target account with the company of the authenticated user. The delete path skips that comparison when the company of the authenticated user is Company::DEFAULT_COMPANY, so a user with a basic role in that company can delete any account of any company of the installation. Deleting an account removes the data held on it, and the last administrative account of a company can be deleted. This gives the attacker the personal data held on the other accounts, including email address, telephone number, postal address and IBAN, and the ability to delete accounts it has no permission to administer.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_