Approved changes feed: RSS · Atom
cpe:2.3:a:lunary-ai:lunary:1.2.4:*:*:*:*:*:*:*
part: a version: 1.2.4 update: *
| Vendor | Lunary Ai (b8ab520b-5869-56bb-8f02-94405305398c) |
|---|---|
| Product | Lunary (bf962528-113b-5365-9dd5-c258cddbc5b5) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-5714 |
vulnerable | 2026-06-08 06:56:17.101480 |
Improper Access Control in lunary-ai/lunary
HIGH (7.4)
In lunary-ai/lunary version 1.2.4, an improper access control vulnerability allows members with team management permissions to manipulate project identifiers in requests, enabling them to invite users to projects in other organizations, change members to projects in other organizations with escalated privileges, and change members from other organizations to their own or other projects, also with escalated privileges. This vulnerability is due to the backend's failure to validate project identifiers against the current user's organization ID and projects belonging to it, as well as a misconfiguration in attribute naming (`org_id` should be `orgId`) that prevents proper user organization validation. As a result, attackers can cause inconsistencies on the platform for affected users and organizations, including unauthorized privilege escalation. The issue is present in the backend API endpoints for user invitation and modification, specifically in the handling of project IDs in requests.
Published: 2024-06-27T18:42:29.236Z
Updated: 2025-10-15T12:49:43.690Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5277 |
vulnerable | 2026-06-08 06:56:15.399053 |
Weak Password Recovery Mechanism in lunary-ai/lunary
MEDIUM (6.4)
In lunary-ai/lunary version 1.2.4, a vulnerability exists in the password recovery mechanism where the reset password token is not invalidated after use. This allows an attacker who compromises the recovery token to repeatedly change the password of a victim's account. The issue lies in the backend's handling of the reset password process, where the token, once used, is not discarded or invalidated, enabling its reuse. This vulnerability could lead to unauthorized account access if an attacker obtains the recovery token.
Published: 2024-06-06T17:46:06.653Z
Updated: 2024-08-01T21:11:12.415Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.