An Insecure Direct Object Reference (IDOR) vulnerability was identified in the `POST /v1/templates` endpoint of the Lunary API, affecting versions up...
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
AI Analyst Comment
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Description Summary:
An Insecure Direct Object Reference (IDOR) vulnerability in the Lunary API allows authenticated users to create unauthorized templates by manipulating the projectId parameter.
Executive Summary:
An IDOR vulnerability in the Lunary API allows authenticated users to create unauthorized project templates, posing a significant risk to data integrity.
Vulnerability Details
CVE-ID: CVE-2025-4962
Affected Software: Lunary Lunary API
Affected Versions: Up to 1.9.22
Vulnerability: This is an Insecure Direct Object Reference (IDOR) flaw located in the POST /v1/templates endpoint. It allows any authenticated user to bypass ownership checks and create templates in projects belonging to other users by modifying the projectId query parameter.
Business Impact
The ability for unauthorized users to manipulate project templates can lead to significant data integrity issues and potential cross-project configuration tampering. With a CVSS score of 7.7, this vulnerability represents a high risk to business operations, as it violates core access control policies and could be leveraged to disrupt project workflows or inject malicious configurations.
Remediation Plan
Immediate Action: Update the Lunary API instance to version 1.9.23 or later, which includes the necessary server-side validation to enforce project ownership.
Proactive Monitoring: Monitor API access logs for irregular POST requests to /v1/templates, specifically looking for discrepancies between user session identifiers and the provided projectId.
Compensating Controls: Implement strict API gateway policies or WAF rules to validate that the authenticated user context matches the requested project resource before the request reaches the backend service.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of August 19, 2025, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability stems from a fundamental lack of server-side authorization checks, making it straightforward to exploit if the attacker can identify target project IDs.
Analyst Recommendation
Given the High severity rating and the confirmation of the flaw's mechanism, administrators must prioritize the update to version 1.9.23. This patch is essential to restore proper access control and prevent unauthorized modification of project data. Please verify your current version and apply the update immediately to eliminate this access control risk.