# CVE-2025-2663: PHPGurukul Bank Locker Management System search-locker-details.php sql injection

> Remote attackers can exploit SQL injection in the search feature to read or modify database contents in the Bank Locker Management System.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2025
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-wjh6-8rr9-qvq6

## What is CVE-2025-2663?

CVE-2025-2663 is a medium-severity SQL injection vulnerability in PHPGurukul Bank Locker Management System, published on 23 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in PHPGurukul Bank Locker Management System 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /search-locker-details.php. The manipulation of the argument searchinput leads to sql injection. The attack can be launched 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-2663?

It affects 1 product.


Products: Phpgurukul Bank Locker Management System.

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

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

## Is CVE-2025-2663 being exploited?

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

## Other vulnerabilities in PHPGurukul Bank Locker Management System

- [CVE-2023-1964](https://insights.sbomify.com/CVE-2023-1964/): PHPGurukul Bank Locker Management System Password Reset recovery.php sql injection (high 7.3)
- [CVE-2023-0562](https://insights.sbomify.com/CVE-2023-0562/): PHPGurukul Bank Locker Management System Login index.php sql injection (high 7.3)
- [CVE-2025-50491](https://insights.sbomify.com/CVE-2025-50491/): Auth bypass in n/a (high 7.1)
- [CVE-2025-2674](https://insights.sbomify.com/CVE-2025-2674/): PHPGurukul Bank Locker Management System aboutus.php sql injection (medium 6.9)
- [CVE-2025-2676](https://insights.sbomify.com/CVE-2025-2676/): PHPGurukul Bank Locker Management System add-subadmin.php sql injection (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2663 is a medium-severity SQL injection vulnerability in PHPGurukul Bank Locker Management System, published on 23 Mar 2025. 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-2025-2663 exists.

Affected product: PHPGurukul Bank Locker Management 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-2663/ (Markdown: https://insights.sbomify.com/CVE-2025-2663/index.md)
```

## Sources

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

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