Slyde is a tool that renders animated presentations from XML. In versions 0.0.4 and earlier, Node.js automatically imports all *.plugin.js or *.plugin.mjs files found under any directory, including node_modules. As a result, any malicious package containing a .plugin.js file can execute arbitrary JavaScript when the package is installed or required by a Slyde project. This flaw enables remote or local execution of code, depending on how the attacker obtains the malicious package. The weakness corresponds to CWE‑829, Improper Control of Generation of Code.

All projects that use the affected loading behavior are vulnerable. The issue applies to any installation of Slyde up to and including version 0.0.4. It is most dangerous when untrusted packages are added to node_modules, such as public npm modules or private packages that the developer does not fully audit. The vendor and product are Tygo‑van‑den‑Hurk’s Slyde, with affected versions 0.0.4 and earlier, running under Node.js.

The vulnerability has a CVSS score of 7.6 and an EPSS below 1 %, indicating a low to moderate likelihood of exploitation in the near term, and it is not listed in the CISA KEV catalog. Exploitation requires an attacker to supply or influence the contents of node_modules in a Slyde project, typically by publishing a malicious dependency or persuading a developer to install one. Because the code runs during the install or require process, an attacker can gain full permission to the machine that runs the Slyde instance. The attack vector is inferred to be local privilege escalation via npm package injection, and, if the Slyde instance is exposed to external users, remote code execution is possible.