vciy

CVE-2024-6785

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.

MXview One and MXview One Central Manager Series store cleartext credentials in a local file

CVE-2024-67854 of 4 sources documented this
22

rank 22 = 0 + 18 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00113  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.1, from NVD  ·  without this subject the record ranks 4

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 22

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 18

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$3,450over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$3,450 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00113 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.00113EPSSNOT IN KEVas of 2026-09-20
Severity6.8 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2024-09-21, 645 days at 0.00, as of 2026-06-28. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
Moxa6.8 MEDIUMreceipt
NVD7.1 HIGHreceipt
Scoring standard
MoxaCVSS v4.0receipt
NVDCVSS v3.1receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running Moxa MXview One Series? Check your version

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.

Reachneeds local access · low privileges required · no user interaction · low attack complexity · no attack requirementsreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-313 Cleartext Storage in a File or on Diskreceipt
Published consequencesCWE-313: Confidentiality: Read Application Data[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in1.3.0; 1.0.0receipt
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, the CNA6.8 MEDIUMreceipt
CVSS, NVD7.1 HIGHreceipt
Exploit probability0.00113 · top 98% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned byMoxareceipt
Recorded changes19 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMoxa MXview One Series; Moxa MXview One Central Manager Seriesreceipt
Published rangesmoxa mxview one < 1.4.1; moxa mxview one central manager 1.0.0receipt
Fixed in1.3.0; 1.0.0receipt

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

The configuration file stores credentials in cleartext. An attacker with local access rights can read or modify the configuration file, potentially resulting in the service being abused due to sensitive information exposure. receipt

NVD's analysis a second authority

severity
7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
weakness
CWE-313; CWE-312
affected versions
moxa mxview one < 1.4.1; moxa mxview one central manager 1.0.0
also scored by
[email protected] 6.8 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · [email protected] 5.5…

The CNA scored it 6.8 and NVD 7.1. Both are shown because both were published; we do not pick one.

check it yourself moxa.com cisa.gov receipt

Movement the material steps

21 Sep 20240.00043
17 Mar 20250.00015 · scoring model v2025.03.14
15 Jun 20260.00114 · scoring model v2026.06.15
28 Jun 20260.00113

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 19 observations
21 Sep 20240.00043
28 Sep 20240.00042
17 Mar 20250.00015
29 Mar 20250.0002
30 Mar 20250.00015
15 Apr 20250.00016
17 Apr 20250.00018
27 May 20250.0002
7 Jun 20250.00023
17 Jun 20250.00026
18 Jul 20250.00027
30 Oct 20250.00068
3 Nov 20250.00073
4 Nov 20250.00056
18 Nov 20250.00025
21 Nov 20250.00056
10 Feb 20260.00076
15 Jun 20260.00114
28 Jun 20260.00113

19 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.00113Published2024-09-21Index as of2026-06-28

Exploit probability more than doubled between 2025-11-18 and 2025-11-21 (0.00025 → 0.00056) and the record had been public for 1 year, 9 months when this index was last written.

Published 2024-09-21 receipt · Index as of 2026-06-28 derived

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

icsa-24-268-05

Of the 3 records in this advisory, this is the only one holding a stated fix version: 1.3.0; 1.0.0.

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

These are index-wide views, not findings about CVE-2024-6785.

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.