CVE-2026-114519: Missing authorization in the Prospero Flow CRM user API allows a basic role user to read and delete other accounts
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::DEFAULTCOMPANY, 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Roskus Prospero Flow CRMto a version that resolves this vulnerability.Fixed in 5.26.0
Event History
Frequently Asked Questions
Which users and accounts are exposed to a basic-role attacker?
Any authenticated basic-role user can read accounts belonging to their own company, including higher-privileged accounts. In versions from 3.5.0, they can also delete accounts in their own company; if the attacker belongs to Company::DEFAULT_COMPANY, they can delete accounts across any company in the installation.
What does an attacker need to exploit this issue?
The attacker needs a valid JSON Web Token for an account with a basic role. The affected API routes require only the auth:api middleware and do not enforce a permission, policy, or role check.
Are deployments affected by default?
The described routes are protected only by JWT authentication, not authorization. Therefore, an installation is affected when it uses the vulnerable versions and exposes these user API routes to basic-role users.
What is the impact of deleting an account?
Deleting an account removes the data held on that account. An attacker can delete the last administrative account of a company, potentially preventing normal administrative access for that company.
How can I determine whether my installation is vulnerable?
Check whether Prospero Flow CRM is version 2.0.0 through versions before 5.26.0. Review routes/api.php and the user read and delete handlers: vulnerable code allows GET /api/user/{id} and DELETE /api/user/{id} with only auth:api and lacks authorization checks in UserReadController::read() and UserDeleteController::delete().