Home/CVE/Client-side JavaScript controls may be bypassed by directly running a JS function to reboot the PLC (e.g., from the brow
CVE
CVE-2022-1667
Client-side JavaScript controls may be bypassed by directly running a JS function to reboot the PLC (e.g., from the brow
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.
HIGH · CVSS 7.5
EPSS 0.01159
EPSS exploitation odds1.16% · top 37%
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2022-1667, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
EPSS exploitation probability
1.16%
Top 37%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Tech impact
partial
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HLifecycle
- 24 Jun 2022Published to NVD
- 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
◆
ATT&CK techniques
1Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques⬡
Weakness Classification
▤
Affected Products & Versions
3secheron sepcos control and protection relay firmware>= 1.23.0 and < 1.23.21
secheron sepcos control and protection relay firmware>= 1.24.0 and < 1.24.8
secheron sepcos control and protection relay firmware>= 1.25.0 and < 1.25.3
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-2022-2102
Controls limiting uploads to certain file extensions may be bypassed. This could...
same CWE-841
CRITICAL
CVE-2022-2105
Client-side JavaScript controls may be bypassed to change user credentials and p...
same CWE-841
CRITICAL
CVE-2022-46710
A logic issue was addressed with improved checks. This issue is fixed in iOS 16....
same CWE-841
MEDIUM
CVE-2023-1383
An Improper Enforcement of Behavioral Workflow vulnerability in the exchangeDevi...
same CWE-841
MEDIUM
CVE-2022-1666
The default password for the web application’s root user (the vendor’s priva...
same product
MEDIUM
CVE-2022-1668
Weak default root user credentials allow remote attackers to easily obtain OS su...
same product
CRITICAL
CVE-2022-2103
An attacker with weak credentials could access the TCP port via an open FTP port...
same product
CRITICAL
CVE-2022-2104
The www-data (Apache web server) account is configured to run sudo with no passw...
same product
CRITICAL
⚑
Vendor Advisories
1cisa-csafcisa-csaf-csaf_files-OT-white-2022-icsa-22-174-03
🔗
References & Sources
1Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.