Skip to main content
VulnerabilityPublished

CVE-2026-120387: Circutor PowerStudio SCADA Wave · Improper Verification of Cryptographic Signature

Affects Circutor PowerStudio SCADA WaveSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 10.0 Critical : upgrade to 24.11.17.0 as a priority.

Data as of 18 Nov 2026, 20:35 UTC

CVSS 4.0 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Circutor)CVSS 4.010.0
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 24.11.17.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Circutor PowerStudio SCADA Wave to 24.11.17.0.

Affected software

ProductAffectedFixed in
CircutorPowerStudio SCADA WaveAffected
  • >=24.8.0 <24.11.17.0
Fixed in
  • 24.11.17.0

AI-suggested

A patch is available in Circutor PowerStudio SCADA Wave version 24.11.17.0. Users should upgrade to this version or later to remediate the vulnerability. No alternative mitigations or temporary fixes are indicated in the advisory.

Description

An improper JWT signature verification vulnerability in CIRCUTOR PowerStudio SCADA WAVE desktop version allows an unauthenticated remote attacker to bypass authentication by submitting an unsigned JWT with the algorithm set to “none”. The shared JWT validation component accepts the token without verifying a cryptographic signature, allowing the attacker to impersonate another user and access protected functionality with that user's privileges.

References

Community reviews

Loading reviews…