Cross-tenant score modification via unchecked run identifier
Published Mar 20, 2025 · Updated Oct 15, 2025
Broken object-level authorization in Lunary 1.6.0 allows remote authenticated users to alter another user's run score. The PATCH /v1/runs/:id/score endpoint uses the attacker-controlled id as the runId_score database key without verifying permission for that run. A valid account is required; exploitation changes stored evaluation data but does not disclose data or interrupt service.
Summary
What happened
Broken object-level authorization in Lunary 1.6.0 allows remote authenticated users to alter another user's run score. The PATCH /v1/runs/:id/score endpoint uses the attacker-controlled id as the runId_score database key without verifying permission for that run. A valid account is required; exploitation changes stored evaluation data but does not disclose data or interrupt service.
The record
- CVE
- CVE-2024-11137
- Published
- Mar 20, 2025
- Updated
- Oct 15, 2025
- Vendor
- Lunary
- Product
- Lunary
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <1.6.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Huntr bounty proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo