CVE-2026-40552 — Remote Code Execution in multiple BinSoft products
Multiple BinSoft products are vulnerable to Remote Command Execution. An authorized user with access to the application and direct access to the backend database can achieve system command execution by uploading an attachment and modifying its storage path in the database to reference an attacker-controlled remote network resource. Alternatively, it is possible to use a previously uploaded file and change its reference. When the application processes the attachment, and a user tries to open it, the referenced resource is executed by the system. Critically, this vulnerability can be exploited by any unauthenticated attacker by chaining it with CVE-2026-40550 and CVE-2026-40551, which allows obtaining database access, and logging onto any account. 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.5% (30-day exploitation probability)+6
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (BinSoft mpCRM, BinSoft mpFaktura, BinSoft mpFirma…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| BinSoft | mpCRM | ≤ 25.2.4 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| BinSoft | mpFaktura | ≤ 26.4.9 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| BinSoft | mpFirma | ≤ 26.4.9 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| BinSoft | mpFirma ERP | ≤ 26.4.9 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| BinSoft | mpGabinet | ≤ 23.12.19 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| BinSoft | mpPOS | ≤ 25.2.4 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| BinSoft | mpSekretariat | ≤ 25.2.4 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| BinSoft | mpWarsztat | ≤ 20.4.28 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 4.7 | CVSS 4.0 | Medium | — | — | cvd@cert.pl via NIST National Vulnerability Database |
| 4.7 | CVSS 4.0 | Medium | — | — | CERT-PL via CVE Program (cve.org) e CISA ADP |
CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:L/SC:H/SI:H/SA:H/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 (score shown at the top: cvd@cert.pl) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.47%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · binsoft/mpgabinet, binsoft/mpfirma, binsoft/mpfaktura, binsoft/mpfirma erp, binsoft/mpsekretariat, binsoft/mppos, binsof
- SSVC assessment updated
- Record published
- CVSS changed · 4.7
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-40550 Privilege Escalation in multiple BinSoft products Apr 28, 2026
- High CVE-2026-40551 Use of Client-Side Authentication in multiple BinSoft products Apr 28, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-40552 is "Remote Code Execution in multiple BinSoft products", rated Medium. It affects mpCRM (BinSoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.7 describes technical severity. EPSS 0.47% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.