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...
Product
Phoenix Contact PLCnext Engineer vulnerabilities
6 published CVES affecting Phoenix Contact PLCnext Engineer, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 4
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest Phoenix Contact PLCnext Engineer CVEs
Newest publication first
-
HighCVSS 8.6 EPSS 0.19%
-
HighCVSS 8.6 EPSS 0.11%
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 unauthenticate...
-
MediumCVSS 6.9 EPSS 0.06%
PLCnext Engineer checks GSDX manifest reference digests but does not cryptographically verify the XML SignatureValue over canonicalized SignedInfo. An unauthenticated local attacker can modify signed GSDML content, update its manifest digest, retain the public certificate data, a...
-
CVE-2023-46144 PHOENIX CONTACT: PLCnext Control prone to download of code without integrity check
PublishedMediumCVSS 6.5 EPSS 0.31%A download of code without integrity check vulnerability in PLCnext products allows an remote attacker with low privileges to compromise integrity on the affected engineering station and the connected devices.
-
HighCVSS 8.8 EPSS 0.75%
A incorrect permission assignment for critical resource vulnerability in PLCnext products allows an remote attacker with low privileges to gain full access on the affected devices.
-
HighCVSS 7.3 EPSS 0.40%
In PHOENIX CONTACT PLCnext Engineer version 2020.3.1 and earlier an improper path sanitation vulnerability exists on import of project files.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.