CVE-2026-43945
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Versions 1.2.11 until 1.3.1 allow an unauthenticated remote attacker to achieve Full Remote Code Execution (RCE) as root. The exploit succeeds even when the platform is configured in its most secure state (Secure Mode Enabled and Node-RED Secure Auth Enabled). Version 1.3.1 fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFUXA versions 1.2.11 through 1.3.1 contain an unauthenticated remote code execution vulnerability that allows attackers to achieve full RCE as root, bypassing all configured security controls including Secure Mode and Node-RED Secure Auth.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FUXA installationCheck if FUXA is running on the system. Look for the FUXA process or check if ports 1881 or 8081 are listening, which are default FUXA ports.Affected if FUXA is found running on the system
-
Determine installed FUXA versionLocate the version file in the FUXA installation directory, typically found in a package.json or version metadata file. Alternatively, access the FUXA web interface and look for an About or Info section that displays the version.Affected if Cannot determine the installed version from available sources
-
Compare version against affected rangeCompare your installed version to the affected range: versions 1.2.11 through 1.3.1 (inclusive). If your version is exactly 1.2.11, 1.2.12, 1.3.0, or 1.3.1, it falls within the affected range.Affected if Installed version is 1.2.11, 1.2.12, 1.3.0, or 1.3.1
-
Check web interface accessibilityDetermine if the FUXA web interface is reachable from network locations outside your trusted administrative network. Check firewall rules and binding addresses in your FUXA configuration.Affected if FUXA web interface is accessible from untrusted or external networks
A system is affected if FUXA is installed with any version between 1.2.11 and 1.3.1, regardless of security settings, and the interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to FUXA version 1.3.1 or later to remediate this critical unauthenticated RCE vulnerability.
1.3.1
- Backup your current FUXA installation including configuration files and any custom dashboards
- Download FUXA version 1.3.1 from the official repository
- Replace the existing installation with the new version, preserving your configuration and data directories
- Restart the FUXA service to apply the update
- Verify the application starts successfully and all functionalities work as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43945 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-43945 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data