Phoenix Contact: Access to CSRF tokens of higher privileged users in MGUARD products
Noroxi assessment
Priority: Monitor (action score 22/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.40% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: PHOENIX CONTACT FL MGUARD 2102 10.4.1; PHOENIX CONTACT FL MGUARD 2105 10.4.1; PHOENIX CONTACT FL MGUARD 4102 PCI 10.4.1.
Low priority for now. Upgrade to PHOENIX CONTACT FL MGUARD 2102 10.4.1; PHOENIX CONTACT FL MGUARD 2105 10.4.1; PHOENIX CONTACT FL MGUARD 4102 PCI 10.4.1 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
A low privileged remote attacker can get access to CSRF tokens of higher privileged users which can be abused to mount CSRF attacks.
- Published
- Sep 10, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 33th percentile
- CWE
- CWE-201
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 5.7
- 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 | tc mguard rs4000 4g vzw vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs4000_4g_vzw_vpn_firmware |
| phoenixcontact | tc mguard rs4000 4g vzw vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs4000_4g_vzw_vpn |
| phoenixcontact | tc mguard rs4000 4g vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs4000_4g_vpn_firmware |
| phoenixcontact | tc mguard rs4000 4g vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs4000_4g_vpn |
| phoenixcontact | tc mguard rs4000 4g att vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs4000_4g_att_vpn_firmware |
| phoenixcontact | tc mguard rs4000 4g att vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs4000_4g_att_vpn |
| phoenixcontact | tc mguard rs4000 3g vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs4000_3g_vpn_firmware |
| phoenixcontact | tc mguard rs4000 3g vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs4000_3g_vpn |
| phoenixcontact | tc mguard rs2000 4g vzw vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs2000_4g_vzw_vpn_firmware |
| phoenixcontact | tc mguard rs2000 4g vzw vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs2000_4g_vzw_vpn |
| phoenixcontact | tc mguard rs2000 4g vpn firmware | cpe:2.3:o:phoenixcontact:tc_mguard_rs2000_4g_vpn_firmware |
| phoenixcontact | tc mguard rs2000 4g vpn | cpe:2.3:h:phoenixcontact:tc_mguard_rs2000_4g_vpn |
and 60 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact fl mguard 2102 firmwarebefore 10.4.1
- phoenixcontact fl mguard 2105 firmwarebefore 10.4.1
- phoenixcontact fl mguard 4102 pci firmwarebefore 10.4.1
- phoenixcontact fl mguard 4102 pcie firmwarebefore 10.4.1
- phoenixcontact fl mguard 4302 firmwarebefore 10.4.1
- phoenixcontact fl mguard 4305 firmwarebefore 10.4.1
- phoenixcontact fl mguard centerport vpn-1000 firmwarebefore 8.9.3
- phoenixcontact fl mguard core tx firmwarebefore 8.9.3
- phoenixcontact fl mguard core tx vpn firmwarebefore 8.9.3
- phoenixcontact fl mguard delta tx/tx firmwarebefore 8.9.3
- phoenixcontact fl mguard delta tx/tx vpn firmwarebefore 8.9.3
- phoenixcontact fl mguard gt/gt firmwarebefore 8.9.3
- phoenixcontact fl mguard gt/gt vpn firmwarebefore 8.9.3
- phoenixcontact fl mguard pci4000 firmwarebefore 8.9.3
- phoenixcontact fl mguard pci4000 vpn firmwarebefore 8.9.3
- phoenixcontact fl mguard pcie4000 firmwarebefore 8.9.3
- phoenixcontact fl mguard pcie4000 vpn firmwarebefore 8.9.3
- phoenixcontact fl mguard rs2000 tx/tx vpn firmwarebefore 8.9.3
- phoenixcontact fl mguard rs2000 tx/tx-b firmwarebefore 8.9.3
- phoenixcontact fl mguard rs2005 tx vpn firmwarebefore 8.9.3
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 FL MGUARD 2102
- before 10.4.1affected · semver
PHOENIX CONTACT FL MGUARD 2105
- before 10.4.1affected · semver
PHOENIX CONTACT FL MGUARD 4102 PCI
- before 10.4.1affected · semver
PHOENIX CONTACT FL MGUARD 4102 PCIE
- before 10.4.1affected · semver
PHOENIX CONTACT FL MGUARD 4302
- before 10.4.1affected · semver
PHOENIX CONTACT FL MGUARD 4305
- before 10.4.1affected · semver
PHOENIX CONTACT FL MGUARD CENTERPORT VPN-1000
- before 8.9.3affected · semver
PHOENIX CONTACT FL MGUARD CORE TX
- before 8.9.3affected · semver
PHOENIX CONTACT FL MGUARD CORE TX VPN
- before 8.9.3affected · semver
PHOENIX CONTACT FL MGUARD DELTA TX/TX
- before 8.9.3affected · semver
PHOENIX CONTACT FL MGUARD DELTA TX/TX VPN
- before 8.9.3affected · semver
PHOENIX CONTACT FL MGUARD GT/GT
- before 8.9.3affected · semver
Same product
phoenixcontact: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-12523Phoenix Contact mGuard Devices versions before 8.8.3: LAN ports get functional after reboot even if they are disabled in the device configuration36Monitor
- CVE-2024-7699Phoenix Contact: OS command execution in MGUARD products35Monitor
- CVE-2024-43388Phoenix Contact: SNMP reconfiguration due to improper input validation in MGUARD devices35Monitor
- CVE-2024-43387Phoenix Contact: Access files due to improper neutralization of special elements in MGUARD devices35Monitor
- CVE-2024-43386Phoenix Contact: OS command execution through EMAIL_NOTIFICATION.TO in mGuard devices.35Monitor
- CVE-2024-43385Phoenix Contact: OS command execution through PROXY_HTTP_PORT in mGuard devices35Monitor
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 FL MGUARD 2102 | 10.4.1 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD 2105 | 10.4.1 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD 4102 PCI | 10.4.1 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD 4102 PCIE | 10.4.1 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD 4302 | 10.4.1 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD 4305 | 10.4.1 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD CENTERPORT VPN-1000 | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD CORE TX | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD CORE TX VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD DELTA TX/TX | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD DELTA TX/TX VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD GT/GT | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD GT/GT VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD PCI4000 | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD PCI4000 VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD PCIE4000 | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD PCIE4000 VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD RS2000 TX/TX VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD RS2000 TX/TX-B | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD RS2005 TX VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD RS4000 TX/TX | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD RS4000 TX/TX VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD RS4000 TX/TX-M | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD RS4000 TX/TX-P | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD RS4004 TX/DTX | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD RS4004 TX/DTX VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD SMART2 | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT FL MGUARD SMART2 VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT TC MGUARD RS2000 3G VPN | 8.9.3 | Vendor (CNA) |
| PHOENIX CONTACT TC MGUARD RS2000 4G ATT VPN | 8.9.3 | Vendor (CNA) |
+6
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.
- Nozomi Networks Security Research Teamreporter
- Andrea PalancaNozomi 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).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-201 · Insertion of Sensitive Information Into Sent DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
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)
- Choosing Message IdentifierCAPEC-12likelihood: High · High
- Exploiting Incorrectly Configured SSL/TLSCAPEC-217likelihood: Low
- WiFi MAC Address TrackingCAPEC-612Low
- WiFi SSID TrackingCAPEC-613Low
- Cellular Broadcast Message RequestCAPEC-618Low
- Signal Strength TrackingCAPEC-619Low
- Analysis of Packet Timing and SizesCAPEC-621Low
- Electromagnetic Side-Channel AttackCAPEC-622Low
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.