CVE-2023-38890
SQLi in Phpgurukul Online Shopping Portal 3.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-38890 is a high-severity SQL Injection (CWE-89) vulnerability in Phpgurukul Online Shopping Portal. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 41% 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.
Online Shopping Portal Project version 3.1 contains a SQL injection vulnerability tracked as CVE-2023-38890. The flaw stems from insufficient validation of user-supplied input in the username field of the login form, allowing remote attackers to inject and execute arbitrary SQL commands or queries. The issue is classified under CWE-89 and carries a CVSS 3.1 base score of 8.8, reflecting high impact on confidentiality, integrity, and availability when successfully exploited.
An authenticated or unauthenticated attacker can submit crafted input through the login form to bypass authentication, extract or modify database contents, and potentially escalate privileges within the application. Public proof-of-concept code and an Exploit-DB entry demonstrate how the injection can be leveraged for unauthorized access and data manipulation without requiring elevated privileges beyond the login interface.
The EPSS score has remained flat at 0.0559 with no material increase since disclosure. Publicly available references include exploit code on GitHub and a technical write-up detailing the injection path, indicating that exploitation details have been shared in the security research community. No official vendor advisories or patches appear among the referenced sources.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-42653
Vulnerability Data
Online Shopping Portal Project 3.1 allows remote attackers to execute arbitrary SQL commands/queries via the login form, leading to unauthorized access and potential data manipulation. This vulnerability arises due to insufficient validation of user-supplied input in the username field, enabling…
more
SQL Injection attacks.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
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.
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.
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.
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.
The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
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.
Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.