CVE-2026-25752
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. An authorization bypass vulnerability in FUXA allows an unauthenticated, remote attacker to modify device tags via WebSockets. Exploitation allows an unauthenticated, remote attacker to bypass role-based access controls and overwrite arbitrary device tags or disable communication drivers, exposing connected ICS/SCADA environments to follow-on actions. This may allow an attacker to manipulate physical processes and disconnected devices from the HMI. This affects FUXA through version 1.2.9. This issue has been patched in FUXA version 1.2.10.
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 before 1.2.10 contains an authorization bypass vulnerability in its WebSocket implementation that allows unauthenticated remote attackers to bypass role-based access controls. Attackers can overwrite arbitrary device tags or disable communication drivers, directly exposing connected ICS/SCADA environments to manipulation of physical processes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.2.10CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
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 installed FUXA versionLocate the version information in the FUXA application interface, typically found in the About section or settings panel, or check the package/version file in the installation directoryAffected if The installed version is prior to 1.2.10 (e.g., 1.2.9, 1.2.8, etc.)
-
Verify WebSocket service accessibilityDetermine if the FUXA WebSocket endpoint (typically on port 1881 or the configured HTTP port with WS protocol) is reachable from network segments that contain untrusted or external systemsAffected if The WebSocket interface is exposed to untrusted networks without firewall restrictions or authentication proxies
-
Confirm WebSocket authentication configurationInspect the FUXA server configuration or logs to determine whether role-based access controls are enforced on WebSocket connections, and whether anonymous or unauthenticated connections are permittedAffected if WebSocket connections can be established without valid authentication credentials or session tokens
-
Check for unauthorized device tag modificationsReview FUXA application logs or audit trails for unexpected or unknown changes to device tag values or configurations that were not performed by authorized usersAffected if Tag modifications exist in logs that cannot be traced to legitimate authenticated user sessions
-
Verify communication driver statusExamine the FUXA runtime status for any communication drivers that have been unexpectedly disabled or stopped, and check logs for the source of those changesAffected if Communication drivers show disabled status with no corresponding authorized administrative action in the audit log
The environment is affected if FUXA version is below 1.2.10 AND the WebSocket interface is accessible to unauthenticated attackers.
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 · scoped1.2.10
Upgrade FUXA to version 1.2.10 or later to remediate the authorization bypass. In production ICS environments, validate the upgrade in a staging environment before deployment.
1.2.10
- Stop the FUXA service
- Backup the current FUXA installation and configuration data
- Download FUXA version 1.2.10 from the official GitHub repository (github.com)
- Replace the existing FUXA files with the version 1.2.10 files
- Verify the integrity of the installation by checking the version number
- Restart the FUXA service
- Verify that WebSocket connections now require proper authorization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25752 — 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-25752 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