Checklist spoofing via missing authorization and slug validation
Published Mar 20, 2025 · Updated Oct 15, 2025
Improper authorization in Lunary before 1.4.26 allows remote authenticated users to create or alter checklists through the API. The checklists.post() endpoint neither verifies the caller's permission nor rejects a slug already assigned to another checklist. Any authenticated user who can reach the endpoint can reuse a legitimate slug, causing malicious checklist data to impersonate or replace trusted content.
Summary
What happened
Improper authorization in Lunary before 1.4.26 allows remote authenticated users to create or alter checklists through the API. The checklists.post() endpoint neither verifies the caller's permission nor rejects a slug already assigned to another checklist. Any authenticated user who can reach the endpoint can reuse a legitimate slug, causing malicious checklist data to impersonate or replace trusted content.
The record
- CVE
- CVE-2024-9000
- Published
- Mar 20, 2025
- Updated
- Oct 15, 2025
- Vendor
- Lunary
- Product
- Lunary
- Classifications
- CWE-862, 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.4.26
What conditions does exploitation require?
What is affected?
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.
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