A CWE-798: Use of Hardcoded Credentials vulnerability exists in Modicon Controllers (All versions of the following CPUs and Communication Mo
A CWE-798: Use of Hardcoded Credentials vulnerability exists in Modicon Controllers (All versions of the following CPUs and Communication Module product references listed in the Security Notifications), which could cause the disclosure of FTP hardcoded credentials when using the Web server of the controller on an unsecure network.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Apr 22, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.2% · 66th percentile
- CWE
- CWE-798
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| schneider-electric | bmx p34x firmware | cpe:2.3:o:schneider-electric:bmx_p34x_firmware |
| schneider-electric | bmx p34x | cpe:2.3:h:schneider-electric:bmx_p34x |
| schneider-electric | bmx noe 0100 firmware | cpe:2.3:o:schneider-electric:bmx_noe_0100_firmware |
| schneider-electric | bmx noe 0100 | cpe:2.3:h:schneider-electric:bmx_noe_0100 |
| schneider-electric | bmx noe 0110 firmware | cpe:2.3:o:schneider-electric:bmx_noe_0110_firmware |
| schneider-electric | bmx noe 0110 | cpe:2.3:h:schneider-electric:bmx_noe_0110 |
| schneider-electric | bmx noc 0401 firmware | cpe:2.3:o:schneider-electric:bmx_noc_0401_firmware |
| schneider-electric | bmx noc 0401 | cpe:2.3:h:schneider-electric:bmx_noc_0401 |
| schneider-electric | tsx p57x firmware | cpe:2.3:o:schneider-electric:tsx_p57x_firmware |
| schneider-electric | tsx p57x | cpe:2.3:h:schneider-electric:tsx_p57x |
| schneider-electric | tsx ety x103 firmware | cpe:2.3:o:schneider-electric:tsx_ety_x103_firmware |
| schneider-electric | tsx ety x103 | cpe:2.3:h:schneider-electric:tsx_ety_x103 |
and 8 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- schneider-electric 140 cpu6x firmwareall versions
- schneider-electric 140 noc 77101 firmwareall versions
- schneider-electric 140 noc 78x00 firmwareall versions
- schneider-electric 140 noe 771x1 firmwareall versions
- schneider-electric bmx noc 0401 firmwareall versions
- schneider-electric bmx noe 0100 firmwareall versions
- schneider-electric bmx noe 0110 firmwareall versions
- schneider-electric bmx p34x firmwareall versions
- schneider-electric tsx ety x103 firmwareall versions
- schneider-electric tsx p57x firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (schneider). Independent of NVD's CPE analysis and usually ahead of it.
n/a Modicon Controllers (All versions of the following CPUs and Communication Module product references listed in the Security Notifications)
- Modicon Controllers (All versions of the following CPUs and Communication Module product references listed in the Security notifications)affected
Same product
schneider-electric: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-6852A CWE-200: Information Exposure vulnerability exists in Modicon Controllers (M340 CPUs, M340 communication modules, Premium CPUs, Premium co30Monitor
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.
- 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
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-798 · Use of Hard-coded CredentialsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
For convenience in support or manufacturing, an account that is identical on every device is embedded in the software. Credentials learned from one device work on all of them.
The bug in code
The whole CWE-798 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const SUPPORT_USER = "support";const SUPPORT_PASS = "hardcoded-password";Fixed
const creds = await provisioning.deviceCredentials(deviceId);if (creds.mustRotate) await forcePasswordChange(deviceId);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
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.