# CVE-2025-5368: PHPGurukul Daily Expense Tracker System expense-yearwise-reports-detailed.php sql injection

> Remote attackers can exploit SQL injection in the todate parameter to read or modify database contents in the Daily Expense Tracker System.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-x94g-xwgg-g5h7

## What is CVE-2025-5368?

CVE-2025-5368 is a medium-severity SQL injection vulnerability in PHPGurukul Daily Expense Tracker System, published on 31 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in PHPGurukul Daily Expense Tracker System 1.1. It has been rated as critical. This issue affects some unknown processing of the file /expense-yearwise-reports-detailed.php. The manipulation of the argument todate leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-5368?

It affects 1 product.


Products: Phpgurukul Daily Expense Tracker System.

## How do I fix CVE-2025-5368?

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

## Is CVE-2025-5368 being exploited?

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

## Other vulnerabilities in PHPGurukul Daily Expense Tracker System

- [CVE-2025-25349](https://insights.sbomify.com/CVE-2025-25349/): SQL injection in n/a (critical 9.8)
- [CVE-2025-25351](https://insights.sbomify.com/CVE-2025-25351/): SQL injection in n/a (critical 9.8)
- [CVE-2020-10106](https://insights.sbomify.com/CVE-2020-10106/): SQL injection in n/a (critical 9.8)
- [CVE-2025-4907](https://insights.sbomify.com/CVE-2025-4907/): PHPGurukul Daily Expense Tracker System forgot-password.php sql injection (medium 6.9)
- [CVE-2025-4908](https://insights.sbomify.com/CVE-2025-4908/): PHPGurukul Daily Expense Tracker System expense-datewise-reports-detailed.php sql injection (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5368 and fix it if it is affected.

What it is: CVE-2025-5368 is a medium-severity SQL injection vulnerability in PHPGurukul Daily Expense Tracker System, published on 31 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5368 exists.

Affected product: PHPGurukul Daily Expense Tracker System. 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-2025-5368/ (Markdown: https://insights.sbomify.com/CVE-2025-5368/index.md)
```

## Sources

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

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