CVE-2019-6814: A CWE-287: Improper Authentication vulnerability exists in the NET55XX Encoder with firmware prior to version 2.1.9.7 which could cause impa
Noroxi assessment
Priority: This week (action score 60/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- A ready-made attack tool exists and the flaw can be exploited over the network without an account, so priority is at least “This week”.
- Probability of exploitation in the next 30 days: 36.6% (FIRST EPSS); higher than 98.5% 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.
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and 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
A CWE-287: Improper Authentication vulnerability exists in the NET55XX Encoder with firmware prior to version 2.1.9.7 which could cause impact to confidentiality, integrity, and availability when a remote attacker crafts a malicious request to the encoder webUI.
- Published
- May 22, 2019
- Updated
- Jun 16, 2026
- EPSS
- 36.6% · 98th percentile
- CWE
- CWE-287
Report tools
Action score
60
This week
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 11 / 30 · 36.6%
- Ready-made attack tool
- 10 / 60 · floor: at least 60
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- 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 |
|---|---|---|
| schneider-electric | net5501 firmware | cpe:2.3:o:schneider-electric:net5501_firmware |
| schneider-electric | net5501 | cpe:2.3:h:schneider-electric:net5501 |
| schneider-electric | net5501-i firmware | cpe:2.3:o:schneider-electric:net5501-i_firmware |
| schneider-electric | net5501-i | cpe:2.3:h:schneider-electric:net5501-i |
| schneider-electric | net5501-xt firmware | cpe:2.3:o:schneider-electric:net5501-xt_firmware |
| schneider-electric | net5501-xt | cpe:2.3:h:schneider-electric:net5501-xt |
| schneider-electric | net5504 firmware | cpe:2.3:o:schneider-electric:net5504_firmware |
| schneider-electric | net5504 | cpe:2.3:h:schneider-electric:net5504 |
| schneider-electric | net5500 firmware | cpe:2.3:o:schneider-electric:net5500_firmware |
| schneider-electric | net5500 | cpe:2.3:h:schneider-electric:net5500 |
| schneider-electric | net5516 firmware | cpe:2.3:o:schneider-electric:net5516_firmware |
| schneider-electric | net5516 | cpe:2.3:h:schneider-electric:net5516 |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- schneider-electric net5500 firmwarebefore 2.1.9.7
- schneider-electric net5501 firmwarebefore 2.1.9.7
- schneider-electric net5501-i firmwarebefore 2.1.9.7
- schneider-electric net5501-xt firmwarebefore 2.1.9.7
- schneider-electric net5504 firmwarebefore 2.1.9.7
- schneider-electric net5508 firmwarebefore 2.1.9.7
- schneider-electric net5516 firmwarebefore 2.1.9.7
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 ÊNET55XX Encoder with firmware prior to version 2.1.9.Ê
- ÊNET55XX Encoder with firmware prior to version 2.1.9.Êaffected
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
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Exploit-DB entry ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | remote | 2019-07-29 |
| Exploit-DB entry | remote | 2019-07-29 |
| Metasploit module | exploit/unix/http/schneider_electric_net55xx_encoderSchneider Electric Pelco Endura NET55XX Encoderexploit | 2019-01-25 |
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.
- Metasploit-118 d
- Published
- First PoC+67 d
- TodayNov 3, 2026+2722 d
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.
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
- 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-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);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)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
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.