# CVE-2023-33831: A remote command execution (RCE) vulnerability in the /api/runscript endpoint of FUXA

> Attackers can execute arbitrary commands on FUXA SCADA systems via a crafted POST request to the runscript endpoint.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-r87q-fq37-pvr6

## What is CVE-2023-33831?

CVE-2023-33831 is a critical command injection vulnerability in n/a, published on 18 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote command execution (RCE) vulnerability in the /api/runscript endpoint of FUXA 1.1.13 allows attackers to execute arbitrary commands via a crafted POST request.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2023-33831?

2 open source packages ship an affected version, including @frangoteam/fuxa. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@frangoteam/fuxa` | npm | All versions to 1.1.13 | None |
| `@frangoteam/fuxa` | npm | All versions to 1.1.13 | None |

Products: Frangoteam Fuxa.

## How do I fix CVE-2023-33831?

No fix has been published for CVE-2023-33831 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-33831 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33831 exists.

Public exploit code:

- Description and exploit of CVE-2023-33831 affecting FUXA web-based Process Visualization (SCADA/HMI/Dashboard) software. (github_poc): https://github.com/rodolfomarianocy/Unauthenticated-RCE-FUXA-CVE-2023-33831
- New exploit for FUXA v1.1.13 - Unauthenticated remote code excecution (github_poc): https://github.com/btar1gan/exploit_CVE-2023-33831
- FUXA - Unauthenticated Remote Code Execution (nuclei): http/cves/2023/CVE-2023-33831.yaml

## Other vulnerabilities in n/a

- [CVE-2026-25893](https://insights.sbomify.com/CVE-2026-25893/): FUXA Unauthenticated Remote Code Execution via Admin JWT Minting (critical 10.0)
- [CVE-2025-69985](https://insights.sbomify.com/CVE-2025-69985/): FUXA has JWT Authentication Bypass via HTTP Referer header spoofing (critical 9.8)
- [CVE-2025-69971](https://insights.sbomify.com/CVE-2025-69971/): FUXA has a hardcoded fallback JWT signing secret (critical 9.8)
- [CVE-2023-31719](https://insights.sbomify.com/CVE-2023-31719/): FUXA SQL Injection vulnerability (critical 9.8)
- [CVE-2026-25894](https://insights.sbomify.com/CVE-2026-25894/): FUXA Unauthenticated Remote Code Execution via Hardcoded JWT Secret in Default Configuration (critical 9.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33831 and fix it if it is affected.

What it is: CVE-2023-33831 is a critical command injection vulnerability in n/a, published on 18 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33831 exists.

Affected packages and fixed versions:
- @frangoteam/fuxa (npm): affected all versions up to 1.1.13; no fix listed
- @frangoteam/fuxa (npm): affected all versions up to 1.1.13; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-33831/ (Markdown: https://insights.sbomify.com/CVE-2023-33831/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-33831
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-33831
- OSV: https://osv.dev/vulnerability/CVE-2023-33831

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-33831/
Summaries are generated and may contain mistakes; the official description above is the record.
