CVE-2026-115328: riclolsen json-scada advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

JSON-SCADA before 0.65-alpha contains an sql injection vulnerability in opcApi() in src/server_realtime_auth/index.js that allows authenticated users to inject SQL via HistoryReadRequest parameters. Attackers can inject stacked statements through NodeId.Id, StartTime, or EndTime values to read, modify, or delete historian data across all locations regardless of role.

Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-22).

Weakness: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 5 references on Exploit Observer

Live scores

EPSS: 0.003
low predicted chance of attack
VEDAS: 0.987
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Suricata

Who is affected

Product	Affected	Not affected
riclolsen json-scada	before 0.65-alpha	0.65-alpha is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Fixed versions stated in the CVE record: 0.65-alpha.

Vendor guidance:

https://github.com/riclolsen/json-scada/commit/60b65bcd42d6ee21aa8587580ec778c3bb9b4755 (patch)
V0.65-alpha Release Notes (release-notes)

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-115328 JSON-SCADA opcApi HistoryRead SQL Injection. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-115328 JSON-SCADA opcApi HistoryRead SQL Injection"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/Invoke/"; fast_pattern; http.request_body; content:"NodeId"; nocase; pcre:"/(union\s+select|\x3b\s*(drop|delete|update|insert|alter)\s|'\s*(or|and)\s*'?\d)/i"; classtype:web-application-attack; reference:cve,CVE-2026-115328; reference:url,https://www.exploit.observer/?keyword=CVE-2026-115328&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=json-scada&match=exact; sid:1082603; rev:1;)

CVE-2026-115328.rules on GitHub

References

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.