# CVE-2025-4962: IDOR Vulnerability in Template Creation via `projectId` Manipulation in lunary-ai/lunary

> Authenticated attackers can create templates in other users' projects by manipulating the projectId parameter due to missing ownership validation.

- **Severity:** High 7.7 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2025
- **Updated:** 18 Aug 2025
- **Also known as:** GHSA-jgvw-vmvx-q85m

## What is CVE-2025-4962?

CVE-2025-4962 is a high-severity missing authorization vulnerability in lunary-ai/lunary, published on 18 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Insecure Direct Object Reference (IDOR) vulnerability was identified in the `POST /v1/templates` endpoint of the Lunary API, affecting versions up to 0.8.8. This vulnerability allows authenticated users to create templates in another user's project by altering the `projectId` query parameter. The root cause of this issue is the absence of server-side validation to ensure that the authenticated user owns the specified `projectId`. The vulnerability has been addressed in version 1.9.23.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-4962?


## How do I fix CVE-2025-4962?

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

## Is CVE-2025-4962 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4962 and fix it if it is affected.

What it is: CVE-2025-4962 is a high-severity missing authorization vulnerability in lunary-ai/lunary, published on 18 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4962 exists.

Affected product: lunary-ai/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-2025-4962/ (Markdown: https://insights.sbomify.com/CVE-2025-4962/index.md)
```

## Sources

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

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