# CVE-2024-29390: SQL injection in n/a

> An attacker can execute arbitrary SQL commands via the item parameter in add-expense.php, potentially reading or modifying database contents.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-7f3w-mgjh-m27h

## What is CVE-2024-29390?

CVE-2024-29390 is a high-severity SQL injection vulnerability in n/a, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Daily Expenses Management System version 1.0, developed by PHP Gurukul, contains a time-based blind SQL injection vulnerability in the 'add-expense.php' page. An attacker can exploit the 'item' parameter in a POST request to execute arbitrary SQL commands in the backend database. This can be done by injecting specially crafted SQL queries that make the database perform time-consuming operations, thereby confirming the presence of the SQL injection vulnerability based on the delay in the server's response.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-29390?

It affects 1 product.


Products: Anujk305 Daily Expenses Management System.

## How do I fix CVE-2024-29390?

No fix has been published for CVE-2024-29390 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-29390 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29390 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29390 and fix it if it is affected.

What it is: CVE-2024-29390 is a high-severity SQL injection vulnerability in n/a, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29390 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-29390/ (Markdown: https://insights.sbomify.com/CVE-2024-29390/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-29390
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-29390
- OSV: https://osv.dev/vulnerability/CVE-2024-29390

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-29390/
Summaries are generated and may contain mistakes; the official description above is the record.