CVE-2025-13175: YSoft SafeQ 6 · Missing Password Field Masking
Affects YSoft SafeQ 6Source CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to MU106 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in MU106
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade YSoft SafeQ 6 to MU106.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| YSoftSafeQ 6 | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-13175, European organizations should: 1) Upgrade YSoft SafeQ 6 to version MU106 or later as soon as the patch becomes available to ensure the password field is properly masked. 2) Restrict administrator UI access strictly to trusted personnel and implement strong authentication and session management controls to prevent unauthorized access. 3) Conduct regular audits of administrator activities and monitor for unusual access patterns to the SafeQ UI. 4) Where possible, avoid using password-protected scan workflow connectors or rotate passwords frequently to limit exposure duration. 5) Educate administrators about the risk of password exposure through browser tools and enforce policies against sharing or storing passwords insecurely. 6) Implement network segmentation and access controls to isolate scanning infrastructure from other critical systems, reducing the impact of credential exposure. 7) Review integration points of scanning workflows with other systems to ensure that compromised credentials cannot be leveraged for further attacks. 8) Maintain an incident response plan that includes steps for credential compromise scenarios related to scanning workflows.
Description
Y Soft SafeQ 6 renders the Workflow Connector password field in a way that allows an administrator with UI access to reveal the value using browser developer/inspection tools. The affected customers are only those with a password-protected scan workflow connector. This issue affects Y Soft SafeQ 6 in versions before MU106.