dbcve.org
BuilderApplication · Todesktop

CVE-2025-67231

MEDIUM · 5.9 CVSS v3.1 Published 2026-01-23
Fix available
A fix is available. Upgrade to 0.33.1 or later.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A reflected cross-site scripting (XSS) vulnerability in ToDesktop Builder v0.33.1 allows attackers to execute arbitrary code in the context of a user's browser via a crafted payload.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A reflected cross-site scripting (XSS) vulnerability in ToDesktop Builder v0.33.1 allows attackers to inject and execute arbitrary JavaScript code in the context of a victim's browser through a crafted malicious payload.

MitigationImplement proper input validation and output encoding on all user-supplied data, and deploy a Content Security Policy (CSP) header to mitigate XSS attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BuilderApplication
Affected:< 0.33.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ToDesktop Builder installation
    Locate the ToDesktop Builder application on the system. Check for the executable or installation directory, typically found in Program Files or the user's application data folder.
    Affected if ToDesktop Builder is installed on the system
  2. Identify installed version
    Right-click the ToDesktop Builder executable, select Properties, and view the File Version details. Alternatively, run the application and check the About or Help menu for the version number.
    Affected if The installed version is lower than 0.33.1
  3. Verify XSS attack surface
    Check if the ToDesktop Builder application exposes any web-based interface, admin panel, or user input fields where malicious scripts could be injected. Review application logs or network traffic for any web endpoints.
    Affected if The application accepts user input through web interfaces or displays user-supplied data without sanitization

A user is affected if ToDesktop Builder version 0.33.1 or higher is NOT installed, and the application exposes input fields or web interfaces that could reflect user-supplied data back to the browser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 0.33.1 or later
Fixed in 0.33.1
Interim mitigation

Implement proper input validation and output encoding on all user-supplied data, and deploy a Content Security Policy (CSP) header to mitigate XSS attacks.

Fix this in Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67231 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data