Is CVE-2026-55550 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55550 being exploited in the wild.

How severe is CVE-2026-55550?

High severity, with a CVSS score of 7.1, published 20 July 2026.

Is there a fix for CVE-2026-55550?

A patch was published on 2026-07-20: Fix available in version 0.12.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55550 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-55550?

Check whether you run Pdovhomilja NextCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55550: NextCRM authorization bypass in MCP product tools

CVE-2026-55550 · Severity: high · CVSS 7.1 · Published 2026-07-20

NextCRM, an open-source customer relationship management platform, contains a security flaw in its product catalog management. While the system is designed to only allow managers and administrators to modify product data, a specific programming interface (API) fails to check these permissions. This allows any standard user with a valid API token to create, change, or delete products, potentially leading to fraudulent pricing, incorrect inventory data, or disruption of sales and invoicing workflows.

Technologies: Pdovhomilja NextCRM. Vendors: Pdovhomilja.

Quick answers

Is CVE-2026-55550 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55550 being exploited in the wild.
How severe is CVE-2026-55550?: High severity, with a CVSS score of 7.1, published 20 July 2026.
Which products and versions are affected?: Pdovhomilja NextCRM 0.12.1.
Is there a fix for CVE-2026-55550?: A patch was published on 2026-07-20: Fix available in version 0.12.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55550 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-55550?: Check whether you run Pdovhomilja NextCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Broken Access Control (BAC) vulnerability exists in NextCRM version 0.12.1 within the Model Context Protocol (MCP) implementation. While standard application server actions enforce Role-Based Access Control (RBAC) using a `requireRole` check for 'manager' or 'admin' roles, the MCP handlers located at `/api/mcp/mcp` (specifically `crm_create_product`, `crm_update_product`, and `crm_delete_product`) fail to perform similar authorization checks. An authenticated attacker with a low-privileged 'user' role can generate a Bearer token and interact directly with these API endpoints to perform unauthorized CRUD operations on the `crm_Products` database table. This bypass allows for the modification of product metadata, pricing, and status. The issue is addressed in version 0.12.3.

Affected products

pdovhomilja nextcrm-app 0.12.1

Timeline

2026-06-13: advisory: Vendor advisory published on GitHub
2026-07-20: disclosed: CVE published to NVD
2026-07-20: patched: Fix available in version 0.12.3

References

https://github.com/pdovhomilja/nextcrm-app/security/advisories/GHSA-wv63-cq38-qg58

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.