dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-59236

MEDIUM · 6.9 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

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 · unedited
Authorization Bypass Through User-Controlled Key (CWE-639) in the Excel import handlers (CustomerImport, LeadImport, ProductImport) in Roskus Prospero Flow CRM before 5.14.0 allows a remote, authenticated user of any role or company to create customer, lead, and product records inside another company's tenant via a spreadsheet whose company_id column points to the victim tenant, uploaded to POST /customer/import/excel/save, which maps company_id directly from the file and performs no check that it matches the authenticated user's company.

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 · high confidence

The Excel import handlers (CustomerImport, LeadImport, ProductImport) in Roskus Prospero Flow CRM before 5.14.0 accept a company_id value directly from uploaded spreadsheet files without validating it against the authenticated user's tenant. This allows any authenticated user to create records in other companies' tenants by specifying a different company_id in the uploaded file.

MitigationImplement authorization checks in all Excel import handlers to verify that the company_id in the uploaded file matches the authenticated user's company context, or ignore the file-provided company_id entirely and use the session-bound company instead.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of Roskus Prospero Flow CRM
    Locate the version file, composer.json, or application metadata that indicates the current software version. Common locations include a version.php file, composer.lock, or the application's about/admin page.
    Affected if The installed version is below 5.14.0, as versions prior to this release contain the vulnerable Excel import handlers.
  2. Verify the Excel import handlers exist in the codebase
    Search for the CustomerImport, LeadImport, and ProductImport PHP classes or handler files within the application's source code, typically under src/Import or similar directories.
    Affected if These import handler classes are present and active in the application.
  3. Confirm the import handlers accept company_id from uploaded files
    Review the code of the Excel import handlers to determine if the company_id column from the uploaded spreadsheet is being processed and used directly without validation against the authenticated user's session.
    Affected if The import handlers read and use a company_id value directly from the uploaded file without cross-referencing it against the current user's tenant or session context.
  4. Check if authenticated users can access the import functionality
    Verify that authenticated users have access to the Excel import feature for customers, leads, or products through the web interface or API endpoints.
    Affected if The import functionality is accessible to authenticated users without additional tenant verification.

You are affected if you are running Roskus Prospero Flow CRM version below 5.14.0 and the Excel import handlers (CustomerImport, LeadImport, ProductImport) are accessible to authenticated users, as they allow tenant isolation bypass via company_id in uploaded files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authorization checks in all Excel import handlers to verify that the company_id in the uploaded file matches the authenticated user's company context, or ignore the file-provided company_id entirely and use the session-bound company instead.

Recommended fix High confidence

5.14.0

  1. 1. Identify the current installed version of Roskus Prospero Flow CRM by checking the application version or codebase
  2. 2. If the current version is below 5.14.0, plan for an upgrade to version 5.14.0 or later
  3. 3. Before upgrading, backup the current database and application files
  4. 4. Perform the upgrade following the project's standard upgrade procedure
  5. 5. After upgrade, verify that the Excel import functionality still works correctly
  6. 6. Confirm that the company_id column in imported spreadsheets is now properly validated against the authenticated user's company

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59236 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59236 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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