Use of Client-Side Authentication in multiple BinSoft products

published 2026-04-28 6mo ago modified 2026-10-26 14d ago also EUVD-2026-26045

cvss: 8.4; version 4.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits: 0; none known

Multiple BinSoft products perform client-side authentication. An attacker with access to any application instance connected to the backend server can bypass the login verification process by manipulating the application binary and authenticate as an arbitrary user.

The described issue affects all published versions. The vendor stated that this issue is a direct result of the architecture model in which the software is distributed, and that it will be mitigated with a corrected installation manual.

Is CVE-2026-40551 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 6mo ago (2026-04-28)

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	4.0	8.4	CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
CNA	4.0	8.4	CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/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

Affected products

BinSoft mpGabinet
BinSoft mpFirma
BinSoft mpFaktura
BinSoft mpFirma ERP
BinSoft mpSekretariat
BinSoft mpPOS
BinSoft mpCRM
BinSoft mpWarsztat

Classification

Weakness

CWE-603 Use of Client-Side Authentication

References

cert.pl /posts/2026/04/CVE-2026-40550/
third-party-advisory
binsoft.pl /produkty
product

Sources

CVE List CVE-2026-40551
NVD CVE-2026-40551

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.