Skip to main content
CVE-2025-67230VulnerabilityPublished

CVE-2025-67230: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-25.

What to do

AI-suggested

To mitigate CVE-2025-67230, organizations should implement strict validation of all custom URL schemes within applications built using ToDesktop Builder. This includes whitelisting allowed protocols and ensuring that any invocation of external handlers is subject to rigorous permission checks. Developers should minimize renderer process privileges and avoid exposing sensitive APIs to untrusted web content. Employing content security policies (CSP) that restrict the sources of executable code and external resources can reduce the risk of renderer compromise. Monitoring and logging attempts to invoke external protocols can help detect exploitation attempts. Until an official patch is released, organizations should consider isolating or sandboxing applications built with vulnerable versions and avoid loading untrusted content. Regularly updating to the latest versions of ToDesktop Builder once patches are available is critical. Security teams should also educate developers about the risks of improper URL scheme handling and encourage secure coding practices. Network-level controls to restrict unauthorized outbound connections initiated by desktop applications may provide an additional layer of defense.

Description

Improper permissions in the handler for the Custom URL Scheme in ToDesktop Builder v0.33.0 allows attackers with renderer-context access to invoke external protocol handlers without sufficient validation.

References

Community reviews

Loading reviews…