CVE
winCRM access control bypass in customer ID parameter
- Exploited
- No known exploitation
- Fix
- Fixed in 11/12/2025
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected products: winCRM web version (online) and desktop versions wincrm.exe and winsat.exe
Summary
winCRM has an Insecure Direct Object Reference (IDOR) flaw that lets a user view the names of other users and companies on the platform. An attacker with low-privilege access can exploit it remotely over the network by changing the numeric customer ID in the ClientesClasificaciones parameter and cycling through values.
Original description
Insecure Direct Object Reference (IDOR) vulnerability. Exploiting this vulnerability allows a user to view the names of other users/companies on the platform by iterating over the numerical value that identifies the customer in 'ClientesClasificaciones' parameter in'/Clientes/ClientesClasificaciones/'.
Who should check
Teams running winCRM, either the online web version or the Windows desktop versions wincrm.exe and winsat.exe, that let users view customer records.
“Web versions: https://www.wincrm.eu/”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected products: winCRM web version (online) and desktop versions wincrm.exe and winsat.exeUpgrade to a fixed version: 11/12/2025.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132212 (Vulnerability in winCRM), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132212 (entry last updated 2026-11-18):
Affected:
- winCRM winCRM: fixed in 11/12/2025
Fixed versions: 11/12/2025.
Conditions (all must be true for the bug to be hit):
- Affected products: winCRM web version (online) and desktop versions wincrm.exe and winsat.exe (source: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-wincrm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-132212 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132212 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-wincrm
- https://www.cve.org/CVERecord?id=CVE-2026-132212
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132212
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132212"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- winCRM winCRM
fixed in 11/12/2025
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132212 |
| Record | NVD · CVE-2026-132212 |
| Other links 1 | |
| Patch | incibe.es · en/incibe-cert/notices/aviso/multiple-vulnerabilities-wincrm |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132212
Is CVE-2026-132212 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A logged-in user can view the names of other users and companies on the platform by iterating over the numerical customer identifier. The advisory describes this as a way to see names the user should not be able to see.Source: incibe.es, cve.org
Which versions are affected by CVE-2026-132212?
winCRM: before 11/12/2025.Source: cve.now feed data
Am I affected, and how do I check?
The range runs from the first version up to the 11/12/2025 fix, and covers the winCRM web version (online) and the desktop versions wincrm.exe and winsat.exe. The facts do not give a version string to compare, so check which release date your installed copy comes from against 11/12/2025.Source: incibe.es, cve.org