PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-105220 klembot CVE debrief

CVE-2026-105220 is a high-severity vulnerability in Twine 2 desktop through 2.12.0 that allows for cross-site scripting (XSS) via imported story files. The vulnerability is due to the importStories() function executing markup from imported story files in the editor window. An attacker can craft a malicious story file that calls the twineElectron openWithScratchFile IPC bridge to write and open a .bat file, leading to code execution as the user.

Vendor
klembot
Product
twinejs
CVSS
HIGH 8.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-04
Original CVE updated
2026-10-04
Advisory published
2026-10-04
Advisory updated
2026-10-04

Who should care

Defenders responsible for Twine 2 desktop installations should assess exposure to this vulnerability and prioritize verification and remediation efforts. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify the version of Twine 2 desktop in use and update to a fixed version as soon as possible.

Why it matters

CVE-2026-105220 is a high-severity vulnerability in Twine 2 desktop through 2.12.0 that allows for cross-site scripting (XSS) via imported story files, potentially leading to code execution as the user.

  • Code execution as the user via crafted story files.
  • Potential for attackers to write and open .bat files.
  • Risk of arbitrary code execution via imported story files.

Technical summary

The vulnerability is due to the importStories() function executing markup from imported story files in the editor window. An attacker can craft a malicious story file that calls the twineElectron openWithScratchFile IPC bridge to write and open a .bat file, leading to code execution as the user. This vulnerability affects Twine 2 desktop through 2.12.0 and allows for cross-site scripting (XSS) via imported story files, potentially leading to code execution as the user. Defenders should prioritize verifying the version of Twine 2 desktop in use and assessing exposure to this vulnerability.

Defensive priority

Defenders should prioritize verifying the version of Twine 2 desktop in use and assessing exposure to this vulnerability. If vulnerable, defenders should update to a fixed version as soon as possible.

Recommended defensive actions

  • Verify the version of Twine 2 desktop in use and assess exposure to this vulnerability.
  • Update to a fixed version as soon as possible.
  • Monitor for suspicious activity related to imported story files.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability was discovered in Twine 2 desktop through 2.12.0. The importStories() function executes markup from imported story files in the editor window, allowing for XSS attacks. An attacker can craft a malicious story file to write and open a .bat file, leading to code execution as the user.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-105220 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-105220

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-105220 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-105220

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.