# CVE-2024-4147: Insufficient Access Control in lunary-ai/lunary

> Attackers can delete prompts belonging to other organizations by manipulating IDs, causing data loss and service disruption for legitimate users.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2026
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-f662-3vxf-4mp9

## What is CVE-2024-4147?

CVE-2024-4147 is a high-severity missing authorization vulnerability in Lunary Lunary, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

## Which versions are affected by CVE-2024-4147?

It affects 1 product.


Products: Lunary Lunary.

## How do I fix CVE-2024-4147?

No fix has been published for CVE-2024-4147 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-4147 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4147 exists.

## Other vulnerabilities in Lunary Lunary

- [CVE-2024-8999](https://insights.sbomify.com/CVE-2024-8999/): Improper Access Control in lunary-ai/lunary (critical 9.8)
- [CVE-2024-9095](https://insights.sbomify.com/CVE-2024-9095/): Improper Authorization in lunary-ai/lunary (critical 9.8)
- [CVE-2024-7456](https://insights.sbomify.com/CVE-2024-7456/): SQL Injection in lunary-ai/lunary (critical 9.8)
- [CVE-2024-4146](https://insights.sbomify.com/CVE-2024-4146/): Incorrect Authorization in lunary-ai/lunary (critical 9.8)
- [CVE-2024-5386](https://insights.sbomify.com/CVE-2024-5386/): Account Hijacking via Password Reset Token Leak in lunary-ai/lunary (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4147 and fix it if it is affected.

What it is: CVE-2024-4147 is a high-severity missing authorization vulnerability in Lunary Lunary, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4147 exists.

Affected product: Lunary Lunary. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-4147/ (Markdown: https://insights.sbomify.com/CVE-2024-4147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4147
- OSV: https://osv.dev/vulnerability/CVE-2024-4147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4147/
Summaries are generated and may contain mistakes; the official description above is the record.
