SQL Injection in lunary-ai/lunary
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| lunary-ai | lunary-ai/lunary | affected |
|
No data.
No data available yet.
No CVSS v4.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.4% (1.410% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lunary
Lunary lunary |
|
| CPEs | cpe:2.3:a:lunary:lunary:1.4.2:*:*:*:*:*:*:* | |
| Vendors & Products |
Lunary
Lunary lunary |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lunary-ai
Lunary-ai lunary-ai\/lunary |
|
| CPEs | cpe:2.3:a:lunary-ai:lunary-ai\/lunary:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Lunary-ai
Lunary-ai lunary-ai\/lunary |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A SQL injection vulnerability exists in the `/api/v1/external-users` route of lunary-ai/lunary version v1.4.2. The `order by` clause of the SQL query uses `sql.unsafe` without prior sanitization, allowing for SQL injection. The `orderByClause` variable is constructed without server-side validation or sanitization, enabling an attacker to execute arbitrary SQL commands. Successful exploitation can lead to complete data loss, modification, or corruption. | |
| Title | SQL Injection in lunary-ai/lunary | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV3_0
|