CVE-2025-14850
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 · uneditedAdvantech WebAccess/SCADA is vulnerable to directory traversal, which may allow an attacker to delete arbitrary files.
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 · moderate confidenceAdvantech WebAccess/SCADA contains a directory traversal vulnerability that allows remote attackers to delete arbitrary files on the system by manipulating file path inputs. The critical CVSS score of 9.1 indicates the vulnerability is exploitable over the network with no authentication required and can lead to complete availability compromise.
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= 9.2.1CVSS 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.
-
Confirm Advantech WebAccess/SCADA installationCheck for the presence of WebAccess/SCADA software in standard installation directories such as C:\Program Files\Advantech\WebAccess\ or C:\WebAccess\, or look for the service named 'WebAccess' in Windows Services.Affected if The software is not present on the system.
-
Identify installed versionLocate the version information in the installation folder, typically in a version.txt, about.ini, or in the executable file properties of waadmin.exe or wabroadfix.exe, or check the Windows Registry under HKLM\SOFTWARE\Advantech\WebAccess\Version.Affected if The installed version is exactly 9.2.1.
-
Verify web service is accessibleConfirm the WebAccess/SCADA web interface is running by accessing the default port (typically port 80 or 8080) or checking if the service 'WebAccess' is in a Running state in Windows Services.Affected if The web service is not running or accessible.
-
Check for exposure to unauthenticated accessVerify whether the web interface is accessible from network endpoints without authentication, particularly the file operation endpoints used for deletion operations.Affected if Unauthenticated file operation endpoints are exposed to network users.
A system is affected if Advantech WebAccess/SCADA version 9.2.1 is installed and its web interface with file deletion functionality is accessible to network users without authentication.
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.
From vendor dataApply vendor patches when available; until then, restrict network access to the SCADA interface using firewalls and network segmentation, and implement strict input validation on all file path parameters.
- 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-2025-14850 — 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-2025-14850 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