vciy

CVE-2024-11301

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.

Improper Enforcement of Unique Constraint in lunary-ai/lunary

CVE-2024-113014 of 4 sources documented this
18

rank 18 = 0 + 16 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00572  ·  without this subject the record ranks 18

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.5, from the CNA  ·  without this subject the record ranks 2

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 18

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 16

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$17,500over 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

$17,500 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00572 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.00572EPSSNOT IN KEVas of 2026-09-20
Severity6.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-03-20, 514 days at 0.01, as of 2026-08-16. 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

Running lunary-ai/lunary? 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 complexityreceipt
ImpactComplete integrity lossreceipt
Scored fromCVSS v3.0 · the CNA's vectorreceipt
Weakness classCWE-837 Improper Enforcement of a Single, Unique Actionreceipt
Published consequencesCWE-837: Other: Varies by Context[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in1.6.3receipt
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.5 MEDIUMreceipt
Exploit probability0.00572 · top 54% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned by@huntr_aireceipt
Recorded changes29 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productlunary-ai/lunaryreceipt
Published rangeslunary < 1.6.3receipt
Fixed in1.6.3receipt

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.

Attack path

Network requestrequires low privilegeslunary-ai/lunaryCWE-837 weaknessIntegrity lossI:Hexploits CWE-837data compromise

What it is stated by the CNA

In lunary-ai/lunary before version 1.6.3, the application allows the creation of evaluators without enforcing a unique constraint on the combination of projectId and slug. This allows an attacker to overwrite existing data by submitting a POST request with the same slug as an existing evaluator. The lack of database constraints or application-layer validation to prevent duplicates exposes the application to data integrity issues. This vulnerability can result in corrupted data and potentially malicious actions, impairing the system's functionality. receipt

NVD's analysis a second authority

weakness
CWE-837
affected versions
lunary < 1.6.3
also scored by
[email protected] 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

check it yourself huntr.com github.com receipt

Movement the material steps

20 Mar 20250.00031
15 Jun 20260.00498 · scoring model v2026.06.15
16 Aug 20260.00572

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

Show all 29 observations
20 Mar 20250.00031
21 Mar 20250.00027
22 Mar 20250.00031
23 Mar 20250.00026
26 Mar 20250.00029
29 Mar 20250.00024
30 Mar 20250.00029
21 Apr 20250.00033
27 May 20250.00039
20 Jul 20250.0005
17 Aug 20250.00056
18 Aug 20250.00017
28 Aug 20250.0002
14 Oct 20250.00021
24 Oct 20250.00024
18 Nov 20250.0008
21 Nov 20250.00024
23 Nov 20250.00026
4 Dec 20250.00032
14 Dec 20250.00036
4 Jan 20260.00039
14 Jan 20260.00043
28 Apr 20260.00055
30 Apr 20260.00192
2 May 20260.0022
15 Jun 20260.00498
21 Jun 20260.00535
24 Jul 20260.00548
16 Aug 20260.00572

29 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.00572Published2025-03-20Index as of2026-08-16

Exploit probability more than doubled between 2026-04-28 and 2026-04-30 (0.00055 → 0.00192) and the record had been public for 1 year, 4 months when this index was last written.

Published 2025-03-20 receipt · Index as of 2026-08-16 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.