Security readout for executives and security teams
Plain-English summary
A flaw in Prospero Flow CRM can let a user access or alter another customer’s supplier records, potentially exposing business data and corrupting tenant ownership. The supplied record rates it critical because exploitation is remotely reachable and can severely affect confidentiality and integrity.
Executive priority
Prioritize emergency assessment and rapid remediation. The issue can expose or corrupt supplier information across customers without affecting availability, creating material confidentiality, integrity, and trust risks. Preserve relevant logs before changes so possible historical misuse can be investigated.
Technical view
CVE-2026-78365 combines insecure direct object reference and missing authorization in the supplier API. The supplied description says an authenticated user can read or modify another company’s supplier record and reassign ownership. It identifies versions 4.0.0 through 5.3.1, although the structured affected-version entry is internally inconsistent.
Likely exposure
Organizations using Prospero Flow CRM 4.0.0 through 5.3.1 may be exposed where users can reach the supplier API. Risk is greatest in multi-tenant deployments because the missing object-level authorization crosses company boundaries. Confirm actual installed versions and API accessibility.
Exploitation context
No supplied source reports active exploitation, and the CVE is not listed as KEV. The CVSS 4.0 vector describes remote, low-complexity exploitation without interaction, but its no-privileges rating conflicts with the narrative requirement for an authenticated user. Treat authentication requirements as needing verification.
Researcher notes
The record maps to CWE-639 and CWE-862. A patch commit and v5.5.3 release are referenced, but the supplied bundle does not explicitly state the first fixed version. The structured version data also conflicts with the narrative range, so validate affected and fixed versions against vendor guidance.
Mitigation direction
- Review the vendor patch commit and v5.5.3 release notes immediately.
- Upgrade according to Roskus guidance after testing compatibility and rollback procedures.
- Restrict supplier API access until remediation is confirmed.
- Monitor and investigate cross-company supplier changes or unexpected ownership reassignment.
Validation and detection
- Inventory every Prospero Flow CRM deployment and record its exact version.
- Confirm whether the supplier API is reachable by ordinary tenant users.
- Review authorization logic for company ownership checks on supplier reads and updates.
- Inspect audit logs for cross-tenant access, modifications, or company ownership changes.
- Verify remediation using authorized test tenants in a non-production environment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-78365 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——Secur0Vulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Roskus/prospero-flow-crm/commit/4a52477e6ed66afa436814c80e7bcd68670dd596CVE reference, Secur0 · patch
- https://github.com/Roskus/prospero-flow-crm/releases/tag/v5.5.3CVE reference, Secur0 · release-notes
- https://secur0.com/en/cna/cve-list/cve-2026-78365-idor-supplier-api-cross-tenant-updateCVE reference, Secur0 · third-party-advisory, technical-description
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.