Skip to content
Fencer Intel
medium 5.5

CVE-2021-34560 json

A vulnerability in WirelessHART-Gateway <= 3.0.9 could lead to information exposure of sensitive information

published 5y ago modified 4mo ago also EUVD-2021-21210

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

In PEPPERL+FUCHS WirelessHART-Gateway <= 3.0.9 a form contains a password field with autocomplete enabled. The stored credentials can be captured by an attacker who gains control over the user's computer. Therefore the user must have logged in at least once.

Is CVE-2021-34560 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-097-01 updated cvss 5.5

Pepperl+Fuchs WirelessHART-Gateway

  • Pepperl+Fuchs WHA-GW-F2D2-0-AS- Z2-ETH 3.0.7, 3.0.8, 3.0.9 Pepperl+Fuchs WHA-GW-F2D2-0-AS- Z2-ETH.EIP 3.0.7, 3.0.8, 3.0.9
    affected: mitigation “Minimize network exposure for affected products and ensure they are not accessible via the Internet.” cert.vde.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • Phoenix Contact WHA-GW-F2D2-0-AS- Z2-ETH
  • Phoenix Contact WHA-GW-F2D2-0-AS- Z2-ETH.EIP

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.