| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 1.13- |
Summary
A vulnerability marked as problematic has been reported in OpenPLC v3. Affected by this vulnerability is an unknown functionality. The manipulation leads to credentials storage. This vulnerability is referenced as CVE-2026-35556. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in OpenPLC v3 (the affected version is unknown) and classified as problematic. This issue affects an unknown code. The manipulation with an unknown input leads to a credentials storage vulnerability. Using CWE to declare the problem leads to CWE-256. Storing a password in plaintext may result in a system compromise. Impacted is confidentiality. The summary by CVE is:
OpenPLC_V3 is vulnerable to a Plaintext Storage of a Password vulnerability that could allow an attacker to retrieve credentials and access sensitive information.
The weakness was published by Shriyans Sudhi as icsa-25-345-10. It is possible to read the advisory at cisa.gov. The identification of this vulnerability is CVE-2026-35556 since 04/06/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/09/2026). The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Credentials storageCWE: CWE-256 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/06/2026 CVE reserved04/09/2026 Advisory disclosed
04/09/2026 VulDB entry created
04/09/2026 VulDB entry last update
Sources
Advisory: icsa-25-345-10Researcher: Shriyans Sudhi
Status: Not defined
CVE: CVE-2026-35556 (🔒)
GCVE (CVE): GCVE-0-2026-35556
GCVE (VulDB): GCVE-100-356675
Entry
Created: 04/09/2026 22:09Changes: 04/09/2026 22:09 (64)
Complete: 🔍
Cache ID: 216:19C:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.