PHOENIX CONTACT: Command Injection in WP 6xxx Web panels
Noroxi assessment
Priority: Monitor (action score 35/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: 1.2% (FIRST EPSS); higher than 68.6% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: PHOENIX CONTACT WP 6070-WVPS 4.0.10; PHOENIX CONTACT WP 6101-WXPS 4.0.10; PHOENIX CONTACT WP 6121-WXPS 4.0.10.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to PHOENIX CONTACT WP 6070-WVPS 4.0.10; PHOENIX CONTACT WP 6101-WXPS 4.0.10; PHOENIX CONTACT WP 6121-WXPS 4.0.10 or later.
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
In PHOENIX CONTACTs WP 6xxx series web panels in versions prior to 4.0.10 a remote attacker with low privileges may use a command injection in a HTTP POST request releated to font configuration operations to gain full access to the device.
- Published
- Aug 8, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 69th percentile
- CWE
- CWE-78
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 8.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
- A fix has been released
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 | wp 6070-wvps firmware | cpe:2.3:o:phoenixcontact:wp_6070-wvps_firmware |
| phoenixcontact | wp 6070-wvps | cpe:2.3:h:phoenixcontact:wp_6070-wvps |
| phoenixcontact | wp 6101-wxps firmware | cpe:2.3:o:phoenixcontact:wp_6101-wxps_firmware |
| phoenixcontact | wp 6101-wxps | cpe:2.3:h:phoenixcontact:wp_6101-wxps |
| phoenixcontact | wp 6121-wxps firmware | cpe:2.3:o:phoenixcontact:wp_6121-wxps_firmware |
| phoenixcontact | wp 6121-wxps | cpe:2.3:h:phoenixcontact:wp_6121-wxps |
| phoenixcontact | wp 6156-whps firmware | cpe:2.3:o:phoenixcontact:wp_6156-whps_firmware |
| phoenixcontact | wp 6156-whps | cpe:2.3:h:phoenixcontact:wp_6156-whps |
| phoenixcontact | wp 6185-whps firmware | cpe:2.3:o:phoenixcontact:wp_6185-whps_firmware |
| phoenixcontact | wp 6185-whps | cpe:2.3:h:phoenixcontact:wp_6185-whps |
| phoenixcontact | wp 6215-whps firmware | cpe:2.3:o:phoenixcontact:wp_6215-whps_firmware |
| phoenixcontact | wp 6215-whps | cpe:2.3:h:phoenixcontact:wp_6215-whps |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact wp 6070-wvps firmwarebefore 4.0.10
- phoenixcontact wp 6101-wxps firmwarebefore 4.0.10
- phoenixcontact wp 6121-wxps firmwarebefore 4.0.10
- phoenixcontact wp 6156-whps firmwarebefore 4.0.10
- phoenixcontact wp 6185-whps firmwarebefore 4.0.10
- phoenixcontact wp 6215-whps firmwarebefore 4.0.10
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 WP 6070-WVPS
- before 4.0.10affected · semver
PHOENIX CONTACT WP 6101-WXPS
- before 4.0.10affected · semver
PHOENIX CONTACT WP 6121-WXPS
- before 4.0.10affected · semver
PHOENIX CONTACT WP 6156-WHPS
- before 4.0.10affected · semver
PHOENIX CONTACT WP 6185-WHPS
- before 4.0.10affected · semver
PHOENIX CONTACT WP 6215-WHPS
- before 4.0.10affected · semver
Same product
phoenixcontact: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-3572PHOENIX CONTACT: OS Command Injection in WP 6xxx Web panels40Plan
- CVE-2023-37861PHOENIX CONTACT: OS Command Injection in WP 6xxx Web panels35Monitor
- CVE-2023-3571PHOENIX CONTACT: OS Command Injection in WP 6xxx Web panels35Monitor
- CVE-2023-3570PHOENIX CONTACT: OS Command Injection in WP 6xxx Web panels35Monitor
- CVE-2023-37862PHOENIX CONTACT: Missing Authorization in WP 6xxx Web panels32Monitor
- CVE-2023-37860PHOENIX CONTACT: Missing Authorization in WP 6xxx Web panels30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PHOENIX CONTACT WP 6070-WVPS | 4.0.10 | Vendor (CNA) |
| PHOENIX CONTACT WP 6101-WXPS | 4.0.10 | Vendor (CNA) |
| PHOENIX CONTACT WP 6121-WXPS | 4.0.10 | Vendor (CNA) |
| PHOENIX CONTACT WP 6156-WHPS | 4.0.10 | Vendor (CNA) |
| PHOENIX CONTACT WP 6185-WHPS | 4.0.10 | Vendor (CNA) |
| PHOENIX CONTACT WP 6215-WHPS | 4.0.10 | Vendor (CNA) |
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.
- Gabriele QuagliarellaNozomi Networksfinder
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0452 · Aug 9, 2023(PHOENIX Endüstriyel Ürünler Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- 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
- Low
- User interaction
- None
- Scope
- Unchanged
- 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.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.