CVE
winCRM access control bypass in customer events endpoint
- 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. Affects winCRM web versions hosted at wincrm.eu
Summary
winCRM has an insecure direct object reference flaw that lets an attacker view the names of other users and companies on the platform. A remote attacker with low-privilege login can exploit it by iterating through the numeric customer identifier in the ClientesEventos parameter at /Clientes/ClientesEventos/.
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 'ClientesEventos' parameter in'/Clientes/ClientesEventos/'.
Who should check
Teams running winCRM, a customer relationship management software, in its web version (wincrm.eu) or desktop versions (wincrm.exe, winsat.exe).
“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.
Affects winCRM web versions hosted at wincrm.euUpgrade 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-132216 (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-132216 (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):
- Affects winCRM web versions hosted at wincrm.eu (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-132216 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132216 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
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-132216
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-132216"}.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-132216 |
| Record | NVD · CVE-2026-132216 |
| 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-132216
Is CVE-2026-132216 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?
An authenticated user can view the names of other users and companies on the platform by iterating over the customer identifier number. The flaw lets one logged-in account read names it should not be able to see.Source: incibe.es
Which versions are affected by CVE-2026-132216?
winCRM: before 11/12/2025.Source: cve.now feed data
Am I affected, and how do I check?
The listed range runs from version 0 up to a fix date of 11/12/2025, and the condition covers winCRM web versions hosted at wincrm.eu. A reader can check whether they use the hosted web version at wincrm.eu, since the advisory names no version command or setting.Source: incibe.es
How do I fix CVE-2026-132216?
The checked facts name no fixed version or vendor patch identifiers, so no upgrade target can be confirmed from them. Check the vendor's advisory or contact winCRM for the fix.Source: incibe.es