Cyber Resilience

CVE-2023-0562

SQLi in Phpgurukul Bank Locker Management System 1.0

Public PoCSQLi
Published
28 January 2023
Modified
21 November 2024
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.44 99th percentile
Risk Priority 82 floored blend · peak EPSS

Summary

CVE-2023-0562 is a high-severity SQL Injection (CWE-89) vulnerability in Phpgurukul Bank Locker Management System. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A SQL injection vulnerability exists in PHPGurukul Bank Locker Management System version 1.0. The flaw resides in the index.php file within the Login component, where unsanitized input to the username parameter is passed directly to database queries. The issue is tracked as CWE-89 and carries a CVSS 3.1 base score of 7.3.

An unauthenticated remote attacker can supply crafted input via the login form to execute arbitrary SQL statements. Successful exploitation may allow extraction or modification of limited data and disruption of application functionality, with a publicly available proof-of-concept demonstrating the attack vector.

The EPSS score for this CVE stands at 0.8445, indicating a high likelihood of exploitation attempts. Public references include detailed technical write-ups and exploit code on GitHub and Vuldb, confirming that the issue has been disclosed and is ready for use by threat actors.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

A vulnerability was found in PHPGurukul Bank Locker Management System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file index.php of the component Login. The manipulation of the argument username leads…

more

to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-219716.

CWE(s)
CWE-89

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-1964Same product: Phpgurukul Bank Locker Management System
CVE-2023-1963Same product: Phpgurukul Bank Locker Management System
CVE-2023-48722Same vendor: Phpgurukul
CVE-2024-10331Same vendor: Phpgurukul
CVE-2024-10159Same vendor: Phpgurukul
CVE-2024-3691Same vendor: Phpgurukul
CVE-2024-25351Same vendor: Phpgurukul
CVE-2024-10298Same vendor: Phpgurukul
CVE-2024-0363Same vendor: Phpgurukul
CVE-2024-8464Same vendor: Phpgurukul

Affected Assets

phpgurukul
bank locker management system
1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.2.5

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

CA-8 Penetration Testing
addresses: CWE-89

Penetration testing uses SQL injection payloads against database interfaces, identifying and supporting fixes for SQL injection weaknesses.

SI-10 Information Input Validation
addresses: CWE-89

Validates query inputs to prevent SQL syntax or command manipulation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.

PR.AT-02 partial match
prevents

Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.

A.5.6 Contact with special interest groups partial match
prevents

Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.

A.5.7 Threat intelligence partial match
prevents

Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.

A.8.25 Secure development life cycle partial match
prevents

Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.

A.8.28 Secure coding partial match
prevents

Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.

References