LCDS LAquis SCADA through 4.3.1.1085 is vulnerable to a control bypass and path traversal.
Priority LOW 37CWE-22Published · Updated
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA.
Summary
LCDS LAquis SCADA through 4.3.1.1085 is vulnerable to a control bypass and path traversal. If an attacker can get a victim to load a malicious els project file and use the play feature, then the attacker can bypass a consent popup and write arbitrary files to OS locations where the user has permission, leading to code execution.
Why it matters now
EPSS 0.01268 69th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:laquisscada:scada:*:*:*:*:*:*:*:* | up to 4.3.1.1085 | Vulnerable | Laquisscada |
- cpe:2.3:a:laquisscada:scada:*:*:*:*:*:*:*:* Versions up to 4.3.1.1085 Vulnerable ·Laquisscada
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2021-41579
- 2026-10-03 Alias added: GHSA-q78c-pv4h-fqw6
References
More Laquisscada Scada vulnerabilities
- TI-2020-15430 Out-of-bounds read in LAquis SCADA CVSS 3.1HIGH 7.8
- TI-2019-08199 Type confusion in LCDS LAquis SCADA CVSS 3.1HIGH 7.8
- TI-2019-08212 Out-of-bounds read in LCDS LAquis SCADA CVSS 3.0LOW 3.3
Sources
- CVE-2021-41579 · CVE Program
- CVE-2021-41579 · NVD
- FIRST EPSS
- GHSA-q78c-pv4h-fqw6 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences