CVE-2024-4147 json
Insufficient Access Control in lunary-ai/lunary
published 2026-02-02 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-32706
- cvss
- 7.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
In lunary-ai/lunary version 1.2.13, an insufficient granularity of access control vulnerability allows users to delete prompts created in other organizations through ID manipulation. The vulnerability stems from the application's failure to validate the ownership of the prompt before deletion, only checking if the user has permissions to delete such resources without verifying if it belongs to the user's project or organization. As a result, users can remove prompts not owned by their organization or project, leading to legitimate users being unable to access the removed prompts and causing information inconsistencies.
Patch / fix
- lunary-ai lunary-ai/lunary 1.2.25
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 9 mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.com https://huntr.com/bounties/3f051943-71ea-414c-a528-cd8b5d82a7ad referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
Affected products
- lunary-ai lunary-ai/lunary
Classification
- Weakness
-
- CWE-1220 Insufficient Granularity of Access Control
References
-
github.com
/lunary-ai/lunary/commit/0755dde1afc2a74ec23b55eee03e4416916cf48f
broken-link
-
huntr.com
/bounties/3f051943-71ea-414c-a528-cd8b5d82a7ad
exploit, patch, third-party-advisory
Sources
- CVE List CVE-2024-4147
- NVD CVE-2024-4147
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.