Signed plug-in validation bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Phoenix Contact | PLCnext Engineer | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Phoenixcontact | Plcnext Engineer |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.108% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.certvde.com/en/advisories/VDE-2026-121/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Phoenixcontact
Phoenixcontact plcnext Engineer |
|
| Vendors & Products |
Phoenixcontact
Phoenixcontact plcnext Engineer |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The PFI plugin framework deploys executable assemblies (DLLs) from a signed plugin package into the local plugin repository and loads them via reflection, but the deployment routine processes archive entries that were never covered by the signature verification. An unauthenticated local attacker can replace an unsigned DLL outside the signed prefix in the archive passes verification and overwrites the legitimate signed assembly at the same destination path. The plugin loader then instantiates the attacker-supplied code without any additional integrity check resulting in a full compromise of the affected systems. | |
| Title | Signed plug-in validation bypass | |
| First Time appeared |
Phoenix Contact
Phoenix Contact plcnext Engineer |
|
| Weaknesses | CWE-494 | |
| CPEs | cpe:2.3:a:phoenix_contact:plcnext_engineer:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Phoenix Contact
Phoenix Contact plcnext Engineer |
|
| References |
| |
| Metrics |
cvssV3_1
|