Path traversal in plug-in deployment
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.190% 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 deployment routine does not validate path components when extracting archive entries to the local plugin repository. Archive entries containing relative path segments such as '..' are not rejected, allowing an unauthenticated local attacker to write files outside the plugin repository to arbitrary locations accessible with the current user's permissions which could result in full system compromise. | |
| Title | Path traversal in plug-in deployment | |
| First Time appeared |
Phoenix Contact
Phoenix Contact plcnext Engineer |
|
| Weaknesses | CWE-22 | |
| CPEs | cpe:2.3:a:phoenix_contact:plcnext_engineer:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Phoenix Contact
Phoenix Contact plcnext Engineer |
|
| References |
| |
| Metrics |
cvssV3_1
|