Skip to content
Fencer Vulns
high 7.5

CVE-2022-1667 json

Secheron SEPCOS Control and Protection Relay

published 2022-06-24 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-24953

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

Summary

Client-side JavaScript controls may be bypassed by directly running a JS function to reboot the PLC (e.g., from the browser console) or by loading the corresponding, browser accessible PHP script

Patch / fix

  • Secheron SEPCOS Control and Protection Relay firmware package 1.23.21, 1.24.8, 1.25.3

Vendor advisories

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

cisa ICSA-22-174-03 updated cvss 7.5

Secheron SEPCOS Control and Protection Relay

  • Secheron SEPCOS Single Package firmware (1.23.xx feature level) < 1.23.21 Secheron SEPCOS Single Package firmware (1.24.xx feature level) < 1.24.8 Secheron SEPCOS Single Package firmware (1.25.xx feature level) < 1.25.3
    affected: fixed in 1.25.3, mitigation “SEPCOS Single Package firmware (1.23.xx feature level): Update to 1.23.22 or higher version” support.secheron.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

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

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

CVSS scores

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

Affected products

  • Secheron SEPCOS Control and Protection Relay firmware package

Classification

Weakness
  • CWE-841 Improper Enforcement of Behavioral Workflow

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.