dbcve.org
Fast\/toolsApplication · Yokogawa

CVE-2025-66595

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A vulnerability has been found in FAST/TOOLS provided by Yokogawa Electric Corporation. This product is vulnerable to Cross-Site Request Forgery (CSRF). When a user accesses a link crafted by an attacker, the user’s account could be compromised. The affected products and versions are as follows: FAST/TOOLS (Packages: RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB) R9.01 to R10.04

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in Yokogawa FAST/TOOLS web application (versions R9.01-R10.04 across packages RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB). The application lacks proper origin validation on state-changing requests, allowing attackers to trick authenticated users into unknowingly executing unwanted actions via malicious links.

MitigationImplement anti-CSRF tokens on all state-changing operations and validate Origin/Referer headers. Apply SameSite=Strict/Lax cookie attributes. Contact Yokogawa for official patches. Consider implementing SameSite cookie attributes as an immediate defense-in-depth measure.

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
Fast\/toolsApplication
Affected:>= r9.01, <= r10.04

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
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed FAST/TOOLS version
    Locate the FAST/TOOLS installation and check the version information, typically found in the software release documentation, About dialog in the web interface, or version files within the installation directory. Consult Yokogawa documentation for version location specifics.
    Affected if The installed version is R9.01, R9.02, R9.03, R9.04, R10.01, R10.02, R10.03, or R10.04 (any version from R9.01 through R10.04 inclusive)
  2. Confirm affected package is deployed
    Identify which FAST/TOOLS packages are installed: RVSVRN (Redundant Virtual Station), UNSVRN (Unified Virtual Station), HMIWEB (Web HMI), FTEES (Flexible TEES), or HMIMOB (Mobile HMI). Check installation manifests or deployed components.
    Affected if Any of these packages (RVSVRN, UNSVRN, HMIWEB, FTEES, HMIMOB) are installed and the version falls within R9.01-R10.04
  3. Verify web interface is accessible
    Determine if the FAST/TOOLS web interface is exposed by checking if the web server component is running and accessible on the expected port (typically ports 80/443 or custom ports configured during installation). Check web server status and network listeners.
    Affected if The web application is accessible remotely or to untrusted networks; CSRF requires the user to access the application via a browser
  4. Inspect state-changing endpoints for origin validation
    Review the web application configuration and HTTP response headers for state-changing operations (POST, PUT, DELETE requests). Check if the application validates Origin or Referer headers on these requests. Use browser developer tools or HTTP proxy to inspect requests.
    Affected if The application does NOT validate Origin or Referer headers on state-changing requests, meaning requests from arbitrary origins are accepted

You are affected if FAST/TOOLS version is between R9.01 and R10.04 inclusive AND the web interface is accessible AND the application lacks origin validation on state-changing operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all state-changing operations and validate Origin/Referer headers. Apply SameSite=Strict/Lax cookie attributes. Contact Yokogawa for official patches. Consider implementing SameSite cookie attributes as an immediate defense-in-depth measure.

Fix this in Fast\/tools Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66595 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66595 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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