# CVE-2026-47721: FUXA: Scheduler API missing admin check enables operator-to-admin escalation via scheduled device actions

> Authenticated operators can escalate privileges to admin and execute server-side scripts by bypassing authorization checks in the scheduler API.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-8ghr-w65f-j3qr

## What is CVE-2026-47721?

CVE-2026-47721 is a medium-severity missing authorization vulnerability in frangoteam FUXA, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.2, POST /api/scheduler and DELETE /api/scheduler in server/api/scheduler/index.js do not consistently enforce authJwt.haveAdminPermission for scheduler settings. An authenticated non-admin operator can create or alter deviceActions that invoke onSetValue or onRunScript, or delete schedules, gaining access to device-value changes and server-side project script execution normally reserved for administrators. Scheduled and repeating actions can continue changing PLC setpoints, safety interlocks, device state, or project data after the operator's session ends. This issue is fixed in version 1.3.2.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-47721?

2 open source packages ship an affected version, including fuxa-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fuxa-server` | npm | All versions to 1.1.14-1243 | None |
| `fuxa-server` | npm | All versions to 1.1.14-1243 | None |

## How do I fix CVE-2026-47721?

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

## Is CVE-2026-47721 being exploited?

There is no known exploitation of CVE-2026-47721 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47721 and fix it if it is affected.

What it is: CVE-2026-47721 is a medium-severity missing authorization vulnerability in frangoteam FUXA, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47721 in the wild and no public exploit code.

Affected packages and fixed versions:
- fuxa-server (npm): affected all versions up to 1.1.14-1243; no fix listed
- fuxa-server (npm): affected all versions up to 1.1.14-1243; 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-2026-47721/ (Markdown: https://insights.sbomify.com/CVE-2026-47721/index.md)
```

## Sources

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

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