vciy

CVE-2024-53691

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.

QTS, QuTS hero

CVE-2024-536914 of 4 sources documented this
55

rank 55 = 18 + 22 + 5 + 10 + 0

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.22857  ·  without this subject the record ranks 37

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.8, from NVD  ·  without this subject the record ranks 33

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-01-14  ·  without this subject the record ranks 50

How much of the world it touches

NVD CPE configurations

20 products in the CPE ranges  ·  without this subject the record ranks 45

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.14Mover the next 30 days, if this record is yours
Movement+$424,000on 2025-09-25, the last material move, 11 months before this reading
Basisassumeda published average, not your estate

$1.14M = $4.99M incident cost x 1 exposure x 0.22857 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.22857EPSSNOT IN KEVas of 2026-09-20
Severity8.7 HIGHreceipt
Harmtotal lossreceipt
Exploitationpublic proof-of-conceptreceipt
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 91 days at 0.23, as of 2026-09-14. arc-rules@v1

Foresight · where to check next

CVE-2024-57728Microsoft WindowsMicrosoft WindowsCVE-2022-30333Microsoft WindowsMicrosoft Windows53691

This record is one instance of CWE-59, improper link resolution before file access ('link following'). The index holds 1733 prior instances of this class, 25 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 signal

Sources disagree here.

Severity score
Qnap8.7 HIGHreceipt
NVD8.8 HIGHreceipt
Scoring standard
QnapCVSS v4.0receipt
NVDCVSS v3.1receipt

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

Running QNAP Systems Inc. QTS? 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.

Reachnetwork-reachable · low privileges required · no user interaction · low attack complexity · no attack requirementsreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-59 Improper Link Resolution Before File Access ('Link Following')receipt
Published consequencesCWE-59: Confidentiality, Integrity, Access Control: Read Files or Directories, Modify Files or Directories, Bypass Protection Mechanism; Other: 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 in5.1.8.2823 build 20240712; 5.2.0.2802 build 20240620receipt
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: Proof-of-concept published · 1 public repository, 2025-01-13.

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

Authority who says so

CVSS, the CNA8.7 HIGHreceipt
CVSS, NVD8.8 HIGHreceipt
Exploit probability0.22857 · top 2% of all CVEsreceipt
Blast breadth5 products across 1 vendorderived
Assigned byqnapreceipt
Recorded changes30 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productQNAP Systems Inc. QTS; QNAP Systems Inc. QuTS heroreceipt
Published rangesqnap qts 5.1.0.2348; qnap qts 5.1.0.2399; qnap qts 5.1.0.2418; qnap qts 5.1.0.2444receipt
Show all 20 published ranges
qnap qts 5.1.0.2348
qnap qts 5.1.0.2399
qnap qts 5.1.0.2418
qnap qts 5.1.0.2444
qnap qts 5.1.0.2466
qnap qts 5.1.1.2491
qnap qts 5.1.2.2533
qnap qts 5.1.3.2578
qnap qts 5.1.4.2596
qnap qts 5.1.5.2645
qnap qts 5.1.5.2679
qnap qts 5.1.6.2722
qnap qts 5.1.7.2770
qnap qts 5.2.0.2737
qnap qts 5.2.0.2744
qnap qts 5.2.0.2782
qnap quts hero h5.1.0.2409
qnap quts hero h5.1.0.2424
qnap quts hero h5.1.0.2453
qnap quts hero h5.1.0.2466
Fixed in5.1.8.2823 build 20240712; 5.2.0.2802 build 20240620receipt

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

A link following vulnerability has been reported to affect several QNAP operating system versions. If exploited, the vulnerability could allow remote attackers who have gained user access to traverse the file system to unintended locations. We have already fixed the vulnerability in the following versions: QTS 5.1.8.2823 build 20240712 and later QTS 5.2.0.2802 build 20240620 and later QuTS hero h5.1.8.2823 build 20240712 and later QuTS hero h5.2.0.2802 build 20240620 and later receipt

NVD's analysis a second authority

severity
8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-59
affected versions
qnap qts 5.1.0.2348; qnap qts 5.1.0.2399; qnap qts 5.1.0.2418; and 17 more, listed in full below
also scored by
[email protected] 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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

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

check it yourself qnap.com receipt

Dated events

2025-03-17EPSS moved 0.00 to 0.102026-01-14EPSS moved 0.15 to 0.492026-06-15EPSS moved 0.48 to 0.20

Movement the material steps

7 Dec 20240.00043
17 Mar 20250.10224 · crossed 0.10 · scoring model v2025.03.14
20 Mar 20250.06714 · crossed 0.10
23 Mar 20250.12022 · crossed 0.10
28 Mar 20250.06714 · crossed 0.10
29 Mar 20250.12022 · crossed 0.10
30 Mar 20250.08832 · crossed 0.10
7 Apr 20250.10711 · crossed 0.10
15 Apr 20250.04796 · crossed 0.10
25 Sep 20250.12403 · crossed 0.10
18 Nov 20250.35051
21 Nov 20250.15199
14 Jan 20260.48939
15 Jun 20260.20112 · scoring model v2026.06.15
14 Sep 20260.22857

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

Show all 27 observations
7 Dec 20240.00043
17 Mar 20250.10224
19 Mar 20250.12022
20 Mar 20250.06714
23 Mar 20250.12022
27 Mar 20250.18443
28 Mar 20250.06714
29 Mar 20250.12022
30 Mar 20250.08832
7 Apr 20250.10711
15 Apr 20250.04796
4 May 20250.03953
5 May 20250.04008
12 Jul 20250.04464
22 Aug 20250.04671
24 Sep 20250.03904
25 Sep 20250.12403
26 Sep 20250.14523
2 Oct 20250.15199
18 Nov 20250.35051
21 Nov 20250.15199
14 Jan 20260.48939
25 Jan 20260.49526
7 Feb 20260.48939
22 Apr 20260.48051
15 Jun 20260.20112
14 Sep 20260.22857

27 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.22857Published2024-12-06Public PoC2025-01-13Index as of2026-09-14

Exploit probability more than doubled between 2025-09-24 and 2025-09-25 (0.03904 → 0.12403) and the record had been public for 1 year, 9 months when this index was last written.

Published 2024-12-06 receipt · Public PoC 2025-01-13 receipt · Index as of 2026-09-14 derived

The pattern, elsewhere

This record is one instance of CWE-59, improper link resolution before file access ('link following'). The index holds 1733 prior instances of this class, 25 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2024-57728nothing comparable heldKEV listed · 2025receipt
CVE-2025-60710 · Microsoft Windows 11 Version 24H2only 1 attribute comparableKEV listed · 2025receipt
CVE-2022-21999 · Microsoft Windows 10 Version 1809only 1 attribute comparableKEV listed · 2022receipt
CVE-2022-30333nothing comparable heldKEV listed · 2022receipt
CVE-2021-41379 · Microsoft Windows 10 Version 1507only 1 attribute comparableKEV listed · 2021receipt
CVE-2020-0638 · Microsoft Windowsonly 1 attribute comparableKEV listed · 2020receipt

"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

1733 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

Its defect family

qnap systems inc. qts

Of the 3 records in this advisory, this is the only one holding a stated fix version: 5.1.8.2823 build 20240712; 5.2.0.2802 build 20240620.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

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

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.