dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-9066

HIGH · 8.7 CVSS v4.0 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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 security issue was discovered within FactoryTalk® ViewPoint, allowing unauthenticated attackers to achieve XXE. Certain SOAP requests can be abused to perform XXE, resulting in a temporary denial-of-service.

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

FactoryTalk ViewPoint contains an XML External Entity (XXE) vulnerability in its SOAP endpoint. Unauthenticated attackers can send specially crafted SOAP requests with malicious XML that references external entities, potentially leading to denial of service.

MitigationDisable external entity processing and DTD support in the XML parser, or apply vendor-provided patches for FactoryTalk ViewPoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm FactoryTalk ViewPoint installation
    Check Program Files/Rockwell Software for FactoryTalk ViewPoint installation directory, or look for the service in Windows Services list named 'FactoryTalk ViewPoint'
    Affected if FactoryTalk ViewPoint is not installed on the system
  2. Identify SOAP web service endpoint availability
    Locate the SOAP endpoint configuration files (typically web.config or similar in the web application directory) and check for exposed .asmx or SOAP service URLs
    Affected if SOAP endpoints are accessible and not disabled
  3. Check XML parser configuration for external entity processing
    Examine the web.config or application configuration files for XML parser settings, specifically look for 'XmlResolver', 'DtdProcessing', or 'ExternalEntityResolver' settings
    Affected if XML external entity processing is enabled (XmlResolver is not set to null/disabled, or DtdProcessing is not set to 'Prohibit' or 'Ignore')
  4. Review installed product version
    Check the installed version through Windows Programs and Features, or look for versioninfo.txt/readme in the installation directory
    Affected if Installed version falls within the affected range (compare to vendor advisory for specific version numbers)
  5. Assess network accessibility of SOAP services
    Test SOAP endpoint accessibility from an unauthorized network perspective by attempting to access the SOAP WSDL URL from external systems
    Affected if SOAP endpoints are exposed to untrusted networks without authentication

The environment is affected if FactoryTalk ViewPoint is installed with accessible SOAP endpoints and XML external entity processing is enabled in the parser configuration.

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

Disable external entity processing and DTD support in the XML parser, or apply vendor-provided patches for FactoryTalk ViewPoint.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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