Skip to main content
Menu
CVEs

CVE

winCRM access control bypass in document creation page

Affects the winCRM web version and the Windows desktop version (wincrm.exe and winsat.exe). No fixed version or patch is named in the available data.

CVE-2026-132210Published Updated Summary written by a model

7.1HighCNA
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 the winCRM web version and the Windows desktop version (wincrm.exe and winsat.exe).

Summary

Vulnerability in winCRM, an insecure direct object reference flaw. A remote attacker with a low-privilege user account can change the numeric customer ID in the idCliente parameter of the /Gestion/DocumentosCrear/ page and see the names of other users and companies on the platform.

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 'idCliente' parameter in'/Gestion/DocumentosCrear/'.

Who should check

Teams running winCRM web (wincrm.eu) or Windows desktop builds (wincrm.exe, winsat.exe), including users with a low-privilege account.

“The following versions of winCRM are affected:”

incibe.es

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • 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 the winCRM web version and the Windows desktop version (wincrm.exe and winsat.exe).
  • Upgrade 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-132210 (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-132210 (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 the winCRM web version and the Windows desktop version (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-132210 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132210 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-132210
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-132210"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • winCRM winCRM

    fixed in 11/12/2025

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132210
RecordNVD · CVE-2026-132210
Other links 1
Patchincibe.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-132210

Is CVE-2026-132210 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 user can view the names of other users and companies on the platform by iterating the numeric customer identifier in the idCliente parameter.Source: incibe.es

Which versions are affected by CVE-2026-132210?

winCRM: before 11/12/2025.Source: cve.now feed data

Am I affected, and how do I check?

The affected range is listed from the earliest release through 11/12/2025, covering the winCRM web version and the Windows desktop version (wincrm.exe and winsat.exe). To check an installation, compare its version against that date in the vendor's release information.Source: incibe.es

How do I fix CVE-2026-132210?

The available data names no fixed version or vendor patch, so no upgrade target can be given. Check the vendor's advisory for an update that addresses the idCliente parameter.Source: incibe.es

More CVEs