vciy

CVE-2019-6441

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

An issue was discovered on Shenzhen Coship RT3050 4.0.0.40, RT3052 4.0.0.48, RT7620 10.0.0.49, WM3300 5.0.0.54, and WM3300 5.0.0.55 devices

CVE-2019-64413 of 4 sources documented this
45

rank 45 = 13 + 25 + 1 + 6 + 0

rank@v1 · this cycle

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.53612  ·  without this subject the record ranks 32

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 20

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-05-17  ·  without this subject the record ranks 44

How much of the world it touches

NVD CPE configurations

5 products in the CPE ranges  ·  without this subject the record ranks 39

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 45

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.68Mover the next 30 days, if this record is yours
Movement+$769,000on 2026-09-06, the last material move
Basisassumeda published average, not your estate

$2.68M = $4.99M incident cost x 1 exposure x 0.53612 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.53612EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementthreshold crossedreceipt
RISING10Risen from 0.06208 to 0.53612 across 34 observations. arc-rules@v1

Foresight · where to check next

SonicWall SonicOSConcurrentCVE-2023-28461Fortinet FortiOS,Fortinet FortiOSOracle Payments6441

This record is one instance of CWE-287, improper authentication. The index holds 4979 prior instances of this class, 49 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Check a version against this record

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.0 · NVD's vectorreceipt
Weakness classCWE-287 Improper Authenticationreceipt
Published consequencesCWE-287: Integrity, Confidentiality, Availability, Access Control: Read Application Data, Gain Privileges or Assume Identity, Execute Unauthorized Code or Commands[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 6 Sep 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.53612 · top 1% of all CVEsreceipt
Blast breadth4 products across 1 vendorderived
Assigned bymitrereceipt
Recorded changes34 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesCoship wm3300 firmware; Coship rt3050 firmware; Coship rt3052 firmware; and 1 morereceipt
Published rangescoship rt3050 firmware 4.0.0.40; coship rt3052 firmware 4.0.0.48; coship rt7620 firmware 10.0.0.49; coship wm3300 firmware 5.0.0.54receipt
Show all 5 published ranges
coship rt3050 firmware 4.0.0.40
coship rt3052 firmware 4.0.0.48
coship rt7620 firmware 10.0.0.49
coship wm3300 firmware 5.0.0.54
coship wm3300 firmware 5.0.0.55

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

An issue was discovered on Shenzhen Coship RT3050 4.0.0.40, RT3052 4.0.0.48, RT7620 10.0.0.49, WM3300 5.0.0.54, and WM3300 5.0.0.55 devices. The password reset functionality of the router doesn't have backend validation for the current password and doesn't require any type of authentication. By making a POST request to the apply.cgi file of the router, the attacker can change the admin username and password of the router. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-287
affected versions
coship rt3050 firmware 4.0.0.40; coship rt3052 firmware 4.0.0.48; coship rt7620 firmware 10.0.0.49; and 2 more, listed in full below

check it yourself packetstormsecurity.com exploit-db.com exploit-db.com packetstormsecurity.com vulmon.com anquanke.com receipt

Dated events

2022-02-04EPSS moved 0.06 to 0.302026-09-06EPSS moved 0.38 to 0.54

Movement the material steps

14 Apr 20210.06208
4 Feb 20220.30487 · crossed 0.10
1 Apr 20220.10212
7 Mar 20230.32015 · scoring model v2023.03.01
8 Feb 20240.18638
17 Mar 20250.38612 · scoring model v2025.03.14
18 Nov 20250.60628 · crossed 0.50
21 Nov 20250.46262 · crossed 0.50
17 May 20260.53595 · crossed 0.50
15 Jun 20260.53612 · scoring model v2026.06.15
23 Aug 20260.38198 · crossed 0.50
30 Aug 20260.53612 · crossed 0.50
5 Sep 20260.38198 · crossed 0.50
6 Sep 20260.53612 · crossed 0.50
Show all 34 observations
14 Apr 20210.06208
4 Feb 20220.30487
1 Apr 20220.10212
7 Mar 20230.32015
13 Jul 20230.31284
14 Nov 20230.30913
7 Jan 20240.29279
8 Feb 20240.18638
26 Feb 20240.22485
12 Mar 20240.22406
30 Mar 20240.22421
16 Apr 20240.22078
5 May 20240.22880
27 Jun 20240.20922
9 Aug 20240.22988
17 Dec 20240.25559
26 Jan 20250.27984
17 Mar 20250.38612
29 Mar 20250.41264
30 Mar 20250.38612
9 May 20250.41018
1 Jun 20250.46262
18 Nov 20250.60628
21 Nov 20250.46262
12 Dec 20250.48505
2 Jan 20260.4809
17 Feb 20260.4726
6 Apr 20260.49558
17 May 20260.53595
15 Jun 20260.53612
23 Aug 20260.38198
30 Aug 20260.53612
5 Sep 20260.38198
6 Sep 20260.53612

34 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.53612Published2019-03-19Index as of2026-09-06

The record had been public for 7 years, 5 months when this index was last written.

Published 2019-03-19 receipt · Index as of 2026-09-06 derived

The pattern, elsewhere

This record is one instance of CWE-287, improper authentication. The index holds 4979 prior instances of this class, 49 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2024-53704 · SonicWall SonicOSmatches 8 of 8KEV listed · 2025receipt
CVE-2025-61882 · Oracle Concurrent Processingmatches 8 of 8KEV listed · 2025receipt
CVE-2023-28461matches 8 of 8KEV listed · 2023receipt
CVE-2022-40684 · Fortinet FortiOS, FortiProxy…matches 8 of 8KEV listed · 2022receipt
CVE-2020-12812 · Fortinet FortiOSmatches 8 of 8KEV listed · 2020receipt
CVE-2026-46817 · Oracle Paymentsmatches 8 of 8KEV listed · 2026receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

4979 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2019-6441.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.