Skip to main content

Prospero Flow CRM EUVDEUVD-2026-55634

| CVE-2026-19433 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-08-10 Secur0 GHSA-8666-8wpq-7c9q
8.6
CVSS 4.0 · Vendor: Secur0
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to any company account
  2. Delivery
    Enumerate contact numeric IDs via sequential integer guessing
  3. Exploit
    POST /contact/save with cross-company contact ID
  4. Execution
    Overwrite victim company contact data
  5. Persist
    GET /contact/export-vcard/{id}
  6. Impact
    Exfiltrate personal data as vCard

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

The attacker must hold a valid authenticated session in any company tenant on the shared Prospero Flow CRM installation (CVSS PR:L confirmed). No elevated privileges, no administrative role, and no special configuration are required - standard user-level access to the contact management UI is sufficient. The vulnerability is present in default installations of any version before 5.4.8. Exploitation is limited to instances where multiple companies share the same CRM deployment; single-company self-hosted instances have no cross-tenant data to exfiltrate or corrupt, but the code flaw still exists. The only practical limiting factor is possession of a valid login credential to any tenant account on the target instance.

Impact

The CVSS 4.0 base score of 8.6 (High) with vector AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H reflects the reality accurately: exploitation is low-complexity and requires only a valid application login, achievable by any of potentially hundreds of tenant users in a shared instance. The dual impact - confidentiality breach via vCard export and integrity breach via blind overwrite - is severe in a CRM context where contacts represent business-critical personal and commercial data. No EPSS score was provided in the intelligence, and the vulnerability is not listed in CISA KEV, indicating no confirmed mass or targeted exploitation at time of analysis. However, the exploitability is trivially automatable by sequentially incrementing the contact ID integer across the full save and export endpoints, making the potential for opportunistic abuse high in any multi-tenant deployment. The absence of a public exploit from Secur0's advisory lowers immediate risk slightly, but the attack primitive requires no tooling beyond a browser or curl.

Exploit ScenarioDerived

An attacker authenticates to Prospero Flow CRM with a legitimate account belonging to their own company, then iterates integer values in POST requests to /contact/save or GET requests to /contact/export-vcard/{id}. Within seconds they can overwrite a competitor's contact records with arbitrary data or download personal contact information (name, email, phone) as vCard files for any contact stored in the shared instance. No exploit toolkit is required - standard HTTP requests with sequential ID values are sufficient.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 10, 2026

Cross-tenant IDOR in Prospero Flow CRM before 5.4.8 allows any authenticated user to blindly overwrite contact records belonging to other companies and exfiltrate their personal data as vCard files, simply by supplying an arbitrary numeric contact ID. The contact save and vCard export endpoints performed no company-scoping on their database queries, so a user authenticated to Company A could tamper with or harvest contacts owned by Company B without any special knowledge beyond a valid integer identifier. No public exploit or CISA KEV listing has been identified at time of analysis, but the vulnerability is trivially exploitable in any multi-tenant deployment and the full fix has been released as v5.4.8 (and later v5.5.3).

RemediationAI

The primary fix is to upgrade Prospero Flow CRM to version 5.4.8 or later; version 5.5.3 is the latest tagged release at https://github.com/Roskus/prospero-flow-crm/releases/tag/v5.5.3 and includes the complete patch. The upstream fix (commit f16b4af2027b17bef7c604c92dbd86cf38082398) scopes all contact queries with an additional where('company_id', Auth::user()->company_id) predicate in ContactExportVCard.php, Supplier/Contact/ContactExportVCard.php, ContactRepository::save(), and SupplierContactRepository::save(). If immediate upgrade is not possible, restrict access to the /contact/save, /contact/export-vcard/{id}, /supplier/contact/save, and /supplier/contact/export-vcard/{id} endpoints via WAF or application firewall to only the originating company's authenticated IP ranges - note this is difficult in shared SaaS environments and does not fully mitigate the flaw. Alternatively, temporarily disabling vCard export functionality eliminates the confidentiality vector; the blind-write path via save would still require a separate control such as read-only database permissions for the application user, which is not a practical workaround and upgrade remains the only reliable fix.

Affected VersionsENISA

Prospero Flow CRM 0 <5.4.8

Affected Packages

euvd prospero_flow_crm fix: 5.4.8

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Prospero Flow CRM is a Laravel-based PHP CRM application that serves multiple companies as tenants within a single installation, storing all contacts in a shared database distinguished by a company_id foreign key. The affected code used Eloquent's findOrFail($id) and find($data['id']) - which retrieve by primary key alone - in four controllers and repositories: ContactExportVCard.php, Supplier/Contact/ContactExportVCard.php, ContactRepository::save(), and SupplierContactRepository::save(). The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key): the integer contact ID is fully controlled by the caller and is never validated against the authenticated user's company boundary before the record is read or written. The CPE cpe:2.3:a:roskus:prospero_flow_crm:*:*:*:*:*:*:*:* confirms all versions prior to 5.4.8 are affected across both the regular and supplier-contact subsystems.

Know when Prospero Flow Crm gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Secur0) PRIMARY 8.6 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 9.6 CRITICAL

Scope changes to other tenants (S:C) because exploitation crosses the multi-tenant authorization boundary; PR:L reflects required authenticated session; no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Secur0).

CVSS VectorVendor: Secur0

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Authorization Bypass Through User-Controlled Key in the contact management component in Roskus Prospero Flow CRM before 5.4.8 allows authenticated users of any company to blindly overwrite the contact data of another company and to download that contact's personal data as a vCard via the contact's numeric identifier, because the save and export operations retrieve the record without constraining the query to the authenticated user's company.

Executive ViewAI

Why It Matters

Prospero Flow CRM versions prior to 5.4.8 contain a critical data isolation flaw allowing any user authenticated to the system to access and exfiltrate customer contact data belonging to other companies. While no public exploit code has been identified, the vulnerability is trivially exploitable and creates immediate risk of data breach, regulatory violations, and customer relationship damage.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Low
niche open-source CRM with limited enterprise footprint
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

43
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-78365 CRITICAL
9.3 Aug 24

Cross-tenant authorization bypass (IDOR/BOLA) in Roskus Prospero Flow CRM 4.0.0 through 5.3.1 lets an authenticated user

CVE-2026-59235 HIGH
8.7 Jul 15

Broken function-level authorization in Prospero Flow CRM before 5.5.3 lets any authenticated low-privileged user (e.g. t

CVE-2026-77759 HIGH
8.7 Aug 21

Cross-tenant transaction data exposure in Roskus Prospero Flow CRM 5.0.0-5.3.5 allows any authenticated user on a shared

CVE-2026-59233 HIGH
8.7 Aug 10

Privilege escalation in Roskus Prospero Flow CRM before version 5.2.1 permits any authenticated user - regardless of ass

CVE-2026-19734 HIGH
8.6 Aug 13

Cross-tenant IDOR in Roskus Prospero Flow CRM before 5.4.7 allows any authenticated user to read sensitive product recor

CVE-2026-19539 HIGH
8.6 Aug 11

Cross-tenant IDOR in Roskus Prospero Flow CRM's ticket management component allows any authenticated user - regardless o

CVE-2026-19870 HIGH
8.6 Aug 14

Cross-tenant payroll data exposure in Roskus Prospero Flow CRM before 5.15.10 enables authenticated users holding standa

CVE-2026-59236 MEDIUM
6.9 Jul 15

Cross-tenant record injection in Roskus Prospero Flow CRM before 5.14.0 allows any authenticated user to silently insert

CVE-2026-59237 MEDIUM
6.9 Jul 16

Cross-tenant IDOR in Roskus Prospero Flow CRM before 5.5.3 allows any authenticated user to read, modify, and delete ord

CVE-2026-59240 MEDIUM
6.9 Jul 27

Unauthorized notification deletion in Prospero Flow CRM allows any authenticated user to delete other users' notificatio

CVE-2026-77780 MEDIUM
5.3 Aug 21

Tenant data boundary failure in Roskus Prospero Flow CRM 4.9.1-5.14.0 allows authenticated users holding transaction and

CVE-2026-82911 MEDIUM
5.1 Sep 04

Order confirmation in Roskus Prospero Flow CRM before 5.15.11 can be triggered by an unauthenticated attacker on behalf

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy