CVE-2024-11137VulnerabilityPublished 20 Mar 2025Updated 15 Oct 2025

CVE-2024-11137: lunary-ai/lunary · Insecure Direct Object Reference

Affects lunary-ai/lunarySource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.6.1 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

7.5High

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

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

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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 2026-10-26.

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 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

Upgrade lunary-ai/lunary to 1.6.1.

Affected software

Product	Affected	Fixed in
GitHublunary-ai/lunary`pkg:github/lunary-ai/lunary`Other threats	Affected >=1.6.0 <1.6.1	Fixed in 1.6.1

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

AI-suggested

European organizations should immediately upgrade lunary-ai/lunary to version 1.6.1 or later, where the vulnerability is fixed. In addition to patching, organizations should implement strict access control policies and audit logs to monitor modifications to run scores, enabling detection of unauthorized changes. Employing role-based access control (RBAC) or attribute-based access control (ABAC) can further restrict who can modify run data. Conduct regular security reviews and penetration testing focusing on API endpoints to identify similar authorization weaknesses. Network segmentation and limiting API access to trusted users and systems can reduce exposure. Finally, educate developers on secure coding practices to prevent IDOR vulnerabilities by enforcing server-side authorization checks on all user-controlled parameters.

Description

An Insecure Direct Object Reference (IDOR) vulnerability exists in the `PATCH /v1/runs/:id/score` endpoint of lunary-ai/lunary version 1.6.0. This vulnerability allows an attacker to update the score data of any run by manipulating the id parameter in the request URL, which corresponds to the `runId_score` in the database. The endpoint does not sufficiently validate whether the authenticated user has permission to modify the specified runId, enabling an attacker with a valid account to modify other users' runId scores by specifying different id values. This issue was fixed in version 1.6.1.

Impact

For European organizations using lunary-ai/lunary, this vulnerability can lead to unauthorized modification of critical scoring data, potentially undermining the integrity of analytics, reporting, or decision-making processes that depend on this data. This could affect sectors relying on AI-driven run evaluations, such as research institutions, AI development companies, or any enterprise integrating lunary-ai/lunary into their workflows. The unauthorized data manipulation could result in incorrect performance metrics, loss of trust in system outputs, and potential compliance issues if data integrity is mandated by regulations. While confidentiality and availability are not directly impacted, the integrity breach could indirectly affect business operations and stakeholder confidence. The ease of exploitation (no privilege escalation or user interaction required) increases the risk of internal or external attackers with valid accounts exploiting this flaw. Organizations failing to upgrade may face reputational damage or operational disruptions if attackers manipulate run scores maliciously.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (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:21 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats