CVE
winCRM.exe unauthorized access via hard-coded credentials
Affects the Windows desktop version of winCRM (winCRM.exe), where hardcoded credentials can be extracted from the executable. The checked facts name no fixed version or patch id.
- Exploited
- No known exploitation
- Fix
- Fixed in 11/12/2025
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 11/12/2025.
Summary
Hardcoded credentials stored in the winCRM.exe application let an attacker over the network, without logging in, extract the login details and gain unauthorized access to the database and SMTP server used by winCRM. The affected software is winCRM.exe from winCRM.
Original description
Hardcoded credentials in the executable file. These can be extracted using the “Strings.exe” tool and could allow an attacker unauthorized access to the database and SMTP server. winCRM.exe
Who should check
Teams running the winCRM Windows desktop client (winCRM.exe), or anyone with it installed
“Desktop versions: wincrm.exe and winsat.exe.”
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
What to do
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-132208 (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-132208 (entry last updated 2026-11-18):
Affected:
- winCRM winCRM.exe: fixed in 11/12/2025
Fixed versions: 11/12/2025.
Conditions (all must be true for the bug to be hit):
- Windows desktop version of winCRM (winCRM.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, no login, no user action.
CISA KEV: CVE-2026-132208 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132208 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-132208
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-132208"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- winCRM winCRM.exe
fixed in 11/12/2025
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132208 |
| Record | NVD · CVE-2026-132208 |
| 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-132208
Is CVE-2026-132208 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?
The executable contains hardcoded credentials that an attacker can extract, which could allow unauthorized access to the winCRM database and SMTP server.Source: incibe.es
Which versions are affected by CVE-2026-132208?
winCRM.exe: before 11/12/2025.Source: cve.now feed data
Am I affected, and how do I check?
The advisory's affected condition is the Windows desktop version of winCRM, listed as wincrm.exe and winsat.exe. The checked product range runs from version 0 up to a fix date of 11/12/2025, so check the desktop executable's version or file date against that date.Source: incibe.es
How do I fix CVE-2026-132208?
The checked facts name no fixed version or patch id, so check the vendor's site for an update to the desktop version of winCRM.Source: incibe.es