vciy

CVE-2021-40381

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 Compro IP70 2.08_7130218, IP570 2.08_7130520, IP60, and TN540 devices

CVE-2021-403813 of 4 sources documented this
30

rank 30 = 6 + 19 + 1 + 4 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.22724  ·  without this subject the record ranks 24

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 11

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-11-24  ·  without this subject the record ranks 29

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$694,000over the next 30 days, if this record is yours
Movement+$105,000on 2025-02-21, the last material move, 1 year, 3 months before this reading
Basisassumeda published average, not your estate

$694,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.22724 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.22724EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementscoring model changedreceipt
RISING10Risen from 0.00416 to 0.22724 across 26 observations. 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

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 lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.

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 15 Jun 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, NVD7.5 HIGHreceipt
Exploit probability0.22724 · top 2% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymitrereceipt
Recorded changes26 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesComprotech ip70 firmware; Comprotech ip570 firmwarereceipt
Published rangescomprotech ip70 firmware 2.08_7130218; comprotech ip570 firmware 2.08_7130520receipt

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 Compro IP70 2.08_7130218, IP570 2.08_7130520, IP60, and TN540 devices. index_MJpeg.cgi allows video access. receipt

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
affected versions
comprotech ip70 firmware 2.08_7130218; comprotech ip570 firmware 2.08_7130520

check it yourself github.com packetstormsecurity.com receipt

Dated events

2022-02-04EPSS moved 0.03 to 0.242023-03-07EPSS moved 0.08 to 0.912026-06-15EPSS moved 0.40 to 0.23

Movement the material steps

2 Sep 20210.00416
4 Feb 20220.23848 · crossed 0.10
1 Apr 20220.08382 · crossed 0.10
7 Mar 20230.906 · crossed 0.10 and 0.50 and 0.90 · scoring model v2023.03.01
25 Mar 20230.88972 · crossed 0.90
7 May 20230.48723 · crossed 0.50
12 Mar 20240.26672
17 Dec 20240.09851 · crossed 0.10
21 Feb 20250.13301 · crossed 0.10
17 Mar 20250.34977 · scoring model v2025.03.14
29 Mar 20250.48083
30 Mar 20250.34977
18 Nov 20250.44997
21 Nov 20250.34977
15 Jun 20260.22724 · scoring model v2026.06.15

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

Show all 26 observations
2 Sep 20210.00416
3 Sep 20210.02742
4 Feb 20220.23848
1 Apr 20220.08382
15 Jul 20220.00885
15 Nov 20220.08382
7 Mar 20230.906
8 Mar 20230.90600
25 Mar 20230.88972
9 Apr 20230.83657
23 Apr 20230.79938
7 May 20230.48723
14 Feb 20240.40973
12 Mar 20240.26672
7 Apr 20240.26999
17 May 20240.21000
17 Dec 20240.09851
21 Feb 20250.13301
11 Mar 20250.13253
17 Mar 20250.34977
29 Mar 20250.48083
30 Mar 20250.34977
18 Nov 20250.44997
21 Nov 20250.34977
24 Nov 20250.39532
15 Jun 20260.22724

26 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.22724Published2021-09-01Index as of2026-06-15

Exploit probability more than doubled between 2021-09-02 and 2021-09-03 (0.00416 → 0.02742) and the record had been public for 4 years, 9 months when this index was last written.

Published 2021-09-01 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2021-40381.

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.