CVE-2026-25895
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. A path traversal vulnerability in FUXA allows an unauthenticated, remote attacker to write arbitrary files to arbitrary locations on the server filesystem. 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 through 1.2.9 contains a path traversal vulnerability allowing an unauthenticated remote attacker to write arbitrary files to arbitrary filesystem locations. This critical flaw requires no authentication or user interaction and can be exploited over the network.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 if FUXA is runningCheck for processes named 'fuxa' or services listening on common FUXA ports (default 1881). Use commands like 'netstat -ano | findstr :1881' or 'ps aux | grep -i fuxa'.Affected if FUXA process is found running on the system
-
Determine installed FUXA versionLocate the version information in the FUXA installation directory. Check package.json, version.txt, or the application startup logs for a version string. Compare against the affected range: versions below 1.2.10 are vulnerable.Affected if Installed version is lower than 1.2.10
-
Verify network accessibility of FUXA web interfaceConfirm the FUXA HTTP server is accessible over the network. Test connectivity to the port (default 1881) from external hosts using curl or telnet: 'curl http://<host>:1881'. The vulnerability is exploitable remotely without authentication.Affected if FUXA web interface is reachable from untrusted networks
-
Check for unauthorized file creationReview filesystem for new or unexpected files in directories outside the expected FUXA data folders, particularly in system directories or web root locations. Check file modification timestamps around the time of potential exploitation.Affected if Unexpected files appear in locations outside the designated FUXA data directory
The environment is affected if FUXA version is below 1.2.10 and the web interface is network-accessible, since the path traversal flaw allows unauthenticated remote attackers to write arbitrary files.
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 this vulnerability. Until patched, restrict network access to FUXA instances and monitor for unauthorized file creation activity.
FUXA version 1.2.10
- 1. Identify the current FUXA version running in your environment
- 2. Create a full backup of the FUXA application directory and any associated data/volumes
- 3. Upgrade FUXA to version 1.2.10 or later by pulling the latest Docker image or using the appropriate installation method for your deployment (e.g., `docker pull frangoteam/fuxa:latest` or specific version tag)
- 4. Restart the FUXA service to apply the updated version
- 5. Verify the upgrade was successful by checking the FUXA web interface and confirming the version displays as 1.2.10 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25895 — 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-25895 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