All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to OS command injection.
Noroxi assessment
Priority: Monitor (action score 37/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: 4.5% (FIRST EPSS); higher than 91.3% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are 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
- Published
- May 17, 2018
- Updated
- Jun 16, 2026
- EPSS
- 4.5% · 91th percentile
- CWE
- CWE-78
Report tools
Action score
37
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.5%
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 | fl switch 3005 firmware | cpe:2.3:o:phoenixcontact:fl_switch_3005_firmware |
| phoenixcontact | fl switch 3005 | cpe:2.3:h:phoenixcontact:fl_switch_3005 |
| phoenixcontact | fl switch 3005t firmware | cpe:2.3:o:phoenixcontact:fl_switch_3005t_firmware |
| phoenixcontact | fl switch 3005t | cpe:2.3:h:phoenixcontact:fl_switch_3005t |
| phoenixcontact | fl switch 3004t-fx firmware | cpe:2.3:o:phoenixcontact:fl_switch_3004t-fx_firmware |
| phoenixcontact | fl switch 3004t-fx | cpe:2.3:h:phoenixcontact:fl_switch_3004t-fx |
| phoenixcontact | fl switch 3004t-fx st firmware | cpe:2.3:o:phoenixcontact:fl_switch_3004t-fx_st_firmware |
| phoenixcontact | fl switch 3004t-fx st | cpe:2.3:h:phoenixcontact:fl_switch_3004t-fx_st |
| phoenixcontact | fl switch 3008 firmware | cpe:2.3:o:phoenixcontact:fl_switch_3008_firmware |
| phoenixcontact | fl switch 3008 | cpe:2.3:h:phoenixcontact:fl_switch_3008 |
| phoenixcontact | fl switch 3008t firmware | cpe:2.3:o:phoenixcontact:fl_switch_3008t_firmware |
| phoenixcontact | fl switch 3008t | cpe:2.3:h:phoenixcontact:fl_switch_3008t |
and 46 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact fl switch 3004t-fx firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3004t-fx st firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3005 firmwareafter 1.0 · up to 1.33 inclusive
- phoenixcontact fl switch 3005t firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3006t-2fx firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3006t-2fx sm firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3006t-2fx st firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3008 firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3008t firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3012e-2fx sm firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3012e-2sfx firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3016 firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3016e firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 3016t firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 4000t-8poe-2sfp-r firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 4008t-2gt-3fx sm firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 4008t-2gt-4fx sm firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 4008t-2sfp firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 4012t 2gt 2fx firmware1.0 and later · up to 1.33 inclusive
- phoenixcontact fl switch 4012t-2gt-2fx st firmware1.0 and later · up to 1.33 inclusive
Same product
phoenixcontact: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-13990The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions prior to 1.35 is vulnerable to brute-force attacks, because of Improper Res40Plan
- CVE-2017-16743An Improper Authorization issue was discovered in PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, and 48xxx Series products running firmware Version 140Plan
- CVE-2018-13992The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions 1.0 to 1.34 allows for plaintext transmission (HTTP) of user credentials by39Monitor
- CVE-2018-10731All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to buffer overflows when hand37Monitor
- CVE-2018-13993The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions 1.0 to 1.34 is prone to CSRF.35Monitor
- CVE-2018-10728All Phoenix Contact managed FL SWITCH 3xxx, 4xxx, 48xx products running firmware version 1.0 to 1.33 are prone to buffer overflows (a differ33Monitor
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
No credits in the CNA record.
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.
- Administrator privileges are 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);execFile("ping", ["-c", "1", host], onResult);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)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.