VulnerabilityPublished 20 Mar 2025Updated 15 Oct 2025

CVE-2024-9096: lunary-ai/lunary · Missing Authorization

Affects lunary-ai/lunarySource CVE Database V5

Not known to be exploited · CVSS 7.6 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score

7.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHublunary-ai/lunary`pkg:github/lunary-ai/lunary`Other threats	Affected =1.4.28	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Implement strict role-based access control (RBAC) on the /checklists/:id PATCH endpoint to ensure only authorized users (e.g., project owners, admins) can modify checklists.
Conduct a thorough audit of all API endpoints to verify proper authorization checks are in place.
Apply any available patches or updates from lunary-ai addressing this vulnerability as soon as they are released.
Introduce monitoring and alerting for unusual checklist modification activities, especially from low-privilege accounts.
Educate project members about the risks of unauthorized changes and enforce the principle of least privilege in user roles.
Consider implementing additional application-layer security controls such as input validation and change approval workflows for critical project data.
Regularly review and update access policies to adapt to organizational changes and emerging threats.

Description

In lunary-ai/lunary version 1.4.28, the /checklists/:id route allows low-privilege users to modify checklists by sending a PATCH request. The route lacks proper access control, such as middleware to ensure that only authorized users (e.g., project owners or admins) can modify checklist data. This vulnerability allows any user associated with the project, regardless of their role, to modify checklists, including changing the slug or data fields, which can lead to tampering with essential project workflows, altering business logic, and introducing errors that undermine integrity.

Impact

For European organizations, this vulnerability poses a significant risk to the integrity and availability of project management data. Unauthorized modifications to checklists can disrupt essential workflows, leading to project delays, miscommunication, and potential financial losses. Altered business logic may cause erroneous decisions or actions based on corrupted data. Since lunary-ai/lunary is used for collaborative project management, the vulnerability could allow insider threats or compromised low-privilege accounts to escalate their impact without detection. This undermines trust in the software and may affect compliance with data integrity and security regulations such as GDPR if project data includes personal or sensitive information. The operational impact could extend to critical infrastructure projects, software development, and other sectors relying on accurate project tracking and management. The ease of exploitation and network accessibility increase the urgency for mitigation in environments where lunary-ai/lunary is deployed.

Summary

CVE-2024-9096 identifies a missing authorization vulnerability (CWE-862) in the lunary-ai/lunary project management software, specifically in version 1.4.28. The vulnerability exists in the /checklists/:id API endpoint, which accepts PATCH requests to modify checklist data. Due to insufficient access control, low-privilege users associated with a project can modify checklists without restriction, bypassing intended role-based permissions. This includes altering critical fields such as the checklist slug and other data elements, which can disrupt project workflows, corrupt business logic, and introduce errors that compromise data integrity. The vulnerability is exploitable remotely over the network without user interaction, requiring only low privileges (i.e., being a project member). The CVSS 3.0 base score of 7.6 reflects a high severity due to the potential for integrity and availability impacts, ease of exploitation, and the broad scope of affected users within a project. No patches or known exploits are currently reported, but the lack of authorization checks represents a significant security gap. Organizations using lunary-ai/lunary should prioritize reviewing and enforcing strict access controls on API endpoints that modify critical project data to prevent unauthorized modifications.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 13:07 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats