Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-2680: A vulnerability was found in PHPGurukul Bank Locker Management System 1.0

46
This week
HIGH 7.3REMOTEDOWNGRADE

CVE-2025-2680 is a high-severity flaw (CVSS 7.3) affecting bank locker management system. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in PHPGurukul Bank Locker Management System 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /edit-assign-locker.php?ltid=1. The manipulation of the argument mobilenumber leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.3 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 57%)
CISA exploited listNo
WeaknessCWE-74, CWE-89
Published2025-03-24
Last modified2026-06-17
Publisher (CNA): VulDB · Vendor: phpgurukul

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

phpgurukul bank locker management system DOWNGRADE
Affected: 1.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0
1. Check installed version
apt-cache policy bank-locker-management-system || rpm -q bank-locker-management-system || bank-locker-management-system --version
2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)
apt-cache madison bank-locker-management-system sudo apt install bank-locker-management-system=<VERSION_BEFORE_1.0> sudo apt-mark hold bank-locker-management-system
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list bank-locker-management-system sudo dnf downgrade bank-locker-management-system-<VERSION_BEFORE_1.0> sudo dnf versionlock add bank-locker-management-system
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-2680?

bank locker management system: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-2680 being exploited?

CVE-2025-2680 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-2680 affect?

CVE-2025-2680 affects bank locker management system. Severity is high (CVSS 7.3). A vulnerability was found in PHPGurukul Bank Locker Management System 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /edit-assign-locker.php?ltid=1. The manipulation of the argu

How urgent is CVE-2025-2680?

Priority 46/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.