Skip to content
Fencer Vulns
high 7.5

CVE-2022-22722 json

A CWE-798: Use of Hard-coded Credentials vulnerability exists that could result in information disclosure.

published 2022-02-04 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-27865

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

A CWE-798: Use of Hard-coded Credentials vulnerability exists that could result in information disclosure. If an attacker were to obtain the SSH cryptographic key for the device and take active control of the local operational network connected to the product they could potentially observe and manipulate traffic associated with product configuration. Affected Product: Easergy P5 (All firmware versions prior to V01.401.101)

Patch / fix

  • Schneider Electric Easergy P5 01.401.101

Vendor advisories

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

cisa ICSA-22-055-03 updated cvss 7.5

Schneider Electric Easergy P5 and P3

  • Schneider Electric Software, LLC Easergy P3 < 30.205 Schneider Electric Software, LLC Easergy P5 All firmware < 01.401.102
    affected: mitigation “Disable the GOOSE service of the product to reduce the risk of exposure. If GOOSE is needed for the application, use it only in a secure local area network.” se.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

2.37% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 5.4 AV:A/AC:M/Au:N/C:P/I:P/A:P

Affected products

  • Schneider Electric Easergy P5

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Vulns 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.