dbcve.org
Fast\/toolsApplication · Yokogawa

CVE-2025-66607

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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. The response header contains an insecure setting. Users could be redirected to malicious sites by an attacker. 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 · high confidence

This is an open redirect vulnerability in FAST/TOOLS where the HTTP response header contains an insecure setting that allows arbitrary URL redirection. Attackers can craft malicious links that leverage this header misconfiguration to redirect users to phishing or malware sites, exploiting the trust relationship between users and the affected Yokogawa web applications.

MitigationImplement strict allowlist-based validation for all redirect URLs in response headers, ensuring only trusted internal destinations are permitted. Review and sanitize all user-controllable input that influences redirect locations, and consider implementing Content-Security-Policy headers to prevent unauthorized redirects.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 directory and check the version information file, or use the application's built-in version check (typically found in Help > About or via command line version flag). Compare the version number against the affected range: r9.01 through r10.04 inclusive.
    Affected if The installed version falls within r9.01 to r10.04 inclusive.
  2. Identify the Fast/tools web interface endpoint
    Determine the base URL of the Fast/tools web application (commonly hosted on port 8080 or 443). Common paths include /fasttools or /webui. Note the hostname and port used.
    Affected if Fast/tools web interface is accessible and serving HTTP/HTTPS responses.
  3. Capture and inspect HTTP response headers
    Use a browser developer tool (Network tab), curl (curl -I https://target), or a packet capture tool to capture response headers from the Fast/tools web application. Specifically look for headers such as Location, X-Frame-Options, or custom redirect headers.
    Affected if Response headers contain a Location header or similar redirect-related header with configurable or user-influenced values.
  4. Test for open redirect vulnerability
    Append a query parameter or path that triggers a redirect (common examples: ?redirect=, ?url=, ?next=) followed by an external domain such as https://example.com. Inspect the HTTP response to see if the Location header reflects the attacker-controlled URL.
    Affected if The application redirects to an arbitrary external URL controllable via input parameters without validation.
  5. Review web server configuration
    Examine the Fast/tools web server configuration files (such as server.xml, web.xml, or equivalent) for redirect rules or URL rewriting configurations that may permit unrestricted redirects.
    Affected if Configuration contains redirect rules that allow arbitrary URL values without allowlist validation.

Your environment is affected if Fast/tools version r9.01 through r10.04 is installed and the web interface permits redirects to arbitrary URLs through HTTP response headers.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based validation for all redirect URLs in response headers, ensuring only trusted internal destinations are permitted. Review and sanitize all user-controllable input that influences redirect locations, and consider implementing Content-Security-Policy headers to prevent unauthorized redirects.

Recommended fix Moderate confidence

R10.05 or later (latest available FAST/TOOLS release)

  1. 1. Identify the current FAST/TOOLS version by checking the product or system documentation.
  2. 2. Obtain the latest FAST/TOOLS release (version R10.05 or later) from Yokogawa Electric Corporation's official download channels or contact their support.
  3. 3. Review the upgrade procedure in the FAST/TOOLS installation and operation manual.
  4. 4. Perform a full backup of the current FAST/TOOLS configuration and data before upgrading.
  5. 5. Execute the upgrade following Yokogawa's official upgrade instructions.
  6. 6. After upgrade, verify that the response headers are properly configured and no longer allow arbitrary redirects.
  7. 7. Test that legitimate redirect functionality works correctly after the fix.
Caveat Review Yokogawa's release notes for any compatibility changes or deprecated features between R9.01-R10.04 and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fast\/tools Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66607 — 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-66607 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