CVE-2023-46141: Phoenix Contact: Automation Worx and classic line controllers prone to Incorrect Permission Assignment for Critical Resource
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.87% (FIRST EPSS); higher than 59% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Incorrect Permission Assignment for Critical Resource vulnerability in multiple products of the PHOENIX CONTACT classic line allow an remote unauthenticated attacker to gain full access of the affected device.
- Published
- Dec 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 59th percentile
- CWE
- CWE-732
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| phoenixcontact | automationworx software suite | cpe:2.3:a:phoenixcontact:automationworx_software_suite |
| phoenixcontact | axc 1050 firmware | cpe:2.3:o:phoenixcontact:axc_1050_firmware |
| phoenixcontact | axc 1050 | cpe:2.3:h:phoenixcontact:axc_1050 |
| phoenixcontact | axc 1050 xc firmware | cpe:2.3:o:phoenixcontact:axc_1050_xc_firmware |
| phoenixcontact | axc 1050 xc | cpe:2.3:h:phoenixcontact:axc_1050_xc |
| phoenixcontact | axc 3050 firmware | cpe:2.3:o:phoenixcontact:axc_3050_firmware |
| phoenixcontact | axc 3050 | cpe:2.3:h:phoenixcontact:axc_3050 |
| phoenixcontact | config\+ | cpe:2.3:a:phoenixcontact:config\+ |
| phoenixcontact | fc 350 pci eth firmware | cpe:2.3:o:phoenixcontact:fc_350_pci_eth_firmware |
| phoenixcontact | fc 350 pci eth | cpe:2.3:h:phoenixcontact:fc_350_pci_eth |
| phoenixcontact | ilc1x0 firmware | cpe:2.3:o:phoenixcontact:ilc1x0_firmware |
| phoenixcontact | ilc1x0 | cpe:2.3:h:phoenixcontact:ilc1x0 |
and 19 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact automationworx software suiteall versions
- phoenixcontact axc 1050 firmwareall versions
- phoenixcontact axc 1050 xc firmwareall versions
- phoenixcontact axc 3050 firmwareall versions
- phoenixcontact config+all versions
- phoenixcontact fc 350 pci eth firmwareall versions
- phoenixcontact ilc 3xx firmwareall versions
- phoenixcontact ilc1x0 firmwareall versions
- phoenixcontact ilc1x1 firmwareall versions
- phoenixcontact pc worxall versions
- phoenixcontact pc worx expressall versions
- phoenixcontact pc worx rt basic firmwareall versions
- phoenixcontact pc worx srtall versions
- phoenixcontact rfc 430 eth-ib firmwareall versions
- phoenixcontact rfc 450 eth-ib firmwareall versions
- phoenixcontact rfc 460r pn 3tx firmwareall versions
- phoenixcontact rfc 470s pn 3tx firmwareall versions
- phoenixcontact rfc 480s pn 4tx firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
PHOENIX CONTACT Automation Worx Software Suite
- allaffected
PHOENIX CONTACT AXC 1050
- allaffected
PHOENIX CONTACT AXC 1050 XC
- allaffected
PHOENIX CONTACT AXC 3050
- allaffected
PHOENIX CONTACT Config+
- allaffected
PHOENIX CONTACT FC 350 PCI ETH
- allaffected
PHOENIX CONTACT ILC 3xx
- allaffected
PHOENIX CONTACT ILC1x0
- allaffected
PHOENIX CONTACT ILC1x1
- allaffected
PHOENIX CONTACT PC Worx
- allaffected
PHOENIX CONTACT PC Worx Express
- allaffected
PHOENIX CONTACT PC WORX RT BASIC
- allaffected
Same product
phoenixcontact: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-12870An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86.36Monitor
- CVE-2019-12869An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86.36Monitor
- CVE-2019-12871An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86.36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-3461Nov 15, 2022 · Buffer Overflow in PHOENIX CONTACT Automationworx Software Suite31Monitor
- ← EarlierCVE-2022-3737Nov 15, 2022 · Out-of-bounds Read in PHOENIX CONTACT Automationworx Software Suite31Monitor
- Later →CVE-2023-46143Dec 14, 2023 · Phoenix Contact: Classic line industrial controllers prone to inadequate integrity check of PLC30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Reid WightmanDigital Bondreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-732 · Incorrect Permission Assignment for Critical ResourceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Privilege AbuseCAPEC-122likelihood: High · Medium
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Exploiting Incorrectly Configured Access Control Security LevelsCAPEC-180likelihood: High · Medium
- Signing Malicious CodeCAPEC-206Very High
- Hijacking a privileged processCAPEC-234Medium
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- File and Directory DiscoveryT1083
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Server Software Component: Terminal Services DLLT1505.005
- Abuse Elevation Control MechanismT1548
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls:Code SigningT1553.002
- Compromise Client Software BinaryT1554
- Hijack Execution Flow:Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.