<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 15:00:53 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-43947</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-43947</link>
      <description>&lt;p&gt;FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Version 1.3.0 has an unauthenticated Remote Code Execution vulnerability when `secureEnabled` is set to `true`. The `POST /api/runscript` endpoint checks authorization against the stored script&amp;#39;s permission by ID, but when `test: true` is set in the request, it compiles and executes attacker-supplied code instead of the stored script&amp;#39;s code. An unauthenticated attacker who knows a valid script ID and name may execute arbitrary code via test mode if at least one server-side script exists and is accessible without restrictive permissions. Script IDs and names can be obtained through the unauthenticated information disclosure in `GET /api/project` (reported separately). The only prerequisite is that at least one server-side script exists in the project. Version 1.3.1 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Version 1.3.0 has an unauthenticated Remote Code Execution vulnerability when `secureEnabled` is set to `true`. The `POST /api/runscript` endpoint checks authorization against the stored script&amp;#39;s permission by ID, but when `test: true` is set in the request, it compiles and executes attacker-supplied code instead of the stored script&amp;#39;s code. An unauthenticated attacker who knows a valid script ID and name may execute arbitrary code via test mode if at least one server-side script exists and is accessible without restrictive permissions. Script IDs and names can be obtained through the unauthenticated information disclosure in `GET /api/project` (reported separately). The only prerequisite is that at least one server-side script exists in the project. Version 1.3.1 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-43947</guid>
    </item>
    <item>
      <title>GHSA-rg3m-cfq7-g6h6 — FUXA Vulnerable to Unauthenticated Remote Code Execution via Script Test Mode Authorization Bypass</title>
      <link>https://db.gcve.eu/vuln/ghsa-rg3m-cfq7-g6h6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fuxa-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An unauthenticated Remote Code Execution vulnerability exists in FUXA when `secureEnabled` is set to `true`. The `POST /api/runscript` endpoint checks authorization against the stored script&amp;#39;s permission by ID, but when `test: true` is set in the request, it compiles and executes attacker-supplied code instead of the stored script&amp;#39;s code. An unauthenticated attacker who knows a valid script ID and name may execute arbitrary code via test mode if at least one server-side script exists and is accessible without restrictive permissions.&lt;/p&gt;
&lt;p&gt;Script IDs and names can be obtained through the unauthenticated information disclosure in `GET /api/project` (reported separately).&lt;/p&gt;
&lt;p&gt;The only prerequisite is that at least one server-side script exists in the project.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Authorization confused deputy in script execution**&lt;/p&gt;
&lt;p&gt;File: `server/runtime/scripts/index.js`, lines 86-103&lt;/p&gt;
&lt;p&gt;The authorization check looks up the stored script by ID and validates the stored script&amp;#39;s `permission` field:&lt;/p&gt;
&lt;p&gt;```javascript
this.isAuthorised = function (_script, permission) {
    const st = scriptModule.getScript(_script);  // finds stored script by _script.id
    if (admin || (st &amp;amp;&amp;amp; (!st.permission || st.permission &amp;amp; permission))) {
        return true;
    }
    return false;
}
```&lt;/p&gt;
&lt;p&gt;When a script has no `permission` field set (or `permission: 0`), the expression `!st.permission` evaluates to `true`, and the check passes for any caller including guests.&lt;/p&gt;
&lt;p&gt;**Guest auto-authentication in the m…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fuxa-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An unauthenticated Remote Code Execution vulnerability exists in FUXA when `secureEnabled` is set to `true`. The `POST /api/runscript` endpoint checks authorization against the stored script&amp;#39;s permission by ID, but when `test: true` is set in the request, it compiles and executes attacker-supplied code instead of the stored script&amp;#39;s code. An unauthenticated attacker who knows a valid script ID and name may execute arbitrary code via test mode if at least one server-side script exists and is accessible without restrictive permissions.&lt;/p&gt;
&lt;p&gt;Script IDs and names can be obtained through the unauthenticated information disclosure in `GET /api/project` (reported separately).&lt;/p&gt;
&lt;p&gt;The only prerequisite is that at least one server-side script exists in the project.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Authorization confused deputy in script execution**&lt;/p&gt;
&lt;p&gt;File: `server/runtime/scripts/index.js`, lines 86-103&lt;/p&gt;
&lt;p&gt;The authorization check looks up the stored script by ID and validates the stored script&amp;#39;s `permission` field:&lt;/p&gt;
&lt;p&gt;```javascript
this.isAuthorised = function (_script, permission) {
    const st = scriptModule.getScript(_script);  // finds stored script by _script.id
    if (admin || (st &amp;amp;&amp;amp; (!st.permission || st.permission &amp;amp; permission))) {
        return true;
    }
    return false;
}
```&lt;/p&gt;
&lt;p&gt;When a script has no `permission` field set (or `permission: 0`), the expression `!st.permission` evaluates to `true`, and the check passes for any caller including guests.&lt;/p&gt;
&lt;p&gt;**Guest auto-authentication in the m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-rg3m-cfq7-g6h6</guid>
    </item>
  </channel>
</rss>
