dbcve.org
Online Shopping PortalApplication · Phpgurukul

CVE-2023-37772

HIGH · 8.8 CVSS v3.1 Published 2023-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Online Shopping Portal Project v3.1 was discovered to contain a SQL injection vulnerability via the Email parameter at /shopping/login.php.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the login form's email parameter at /shopping/login.php allows unauthenticated attackers to inject malicious SQL queries, potentially enabling authentication bypass or exfiltration of sensitive database content.

MitigationReplace dynamic SQL queries with parameterized statements/prepared statements for all user inputs, particularly the email parameter; implement strict input validation and consider WAF deployment as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Online Shopping PortalApplication
Affected:= 3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm product installation
    Locate the file /shopping/login.php in your web root directory. This file is present only if the Phpgurukul Online Shopping Portal is installed.
    Affected if The file /shopping/login.php exists in your web server's document root.
  2. Verify product version
    Check the version number in the source code. Common locations include: a config.php file, the footer of PHP pages, or a README/changelog file. Search for a version string like '3.1' or 'Version 3.1'.
    Affected if The installed version is exactly 3.1.
  3. Inspect the login form code
    Open /shopping/login.php and locate the HTML form. Verify it contains an input field named 'email' or similar for the email parameter.
    Affected if The login form contains an email input field that submits to /shopping/login.php or processes login credentials.
  4. Check for vulnerable SQL handling
    Open the file that processes the login form (often /shopping/login.php itself or a connected file). Search for SQL queries that concatenate or embed the email parameter directly into a query string without using prepared statements or parameter binding.
    Affected if The code constructs SQL queries by directly inserting the email parameter into the query string (e.g., "SELECT * FROM users WHERE email='" . $_POST['email'] . "'").

You are affected if the Phpgurukul Online Shopping Portal version 3.1 is installed and the login processing code uses direct string concatenation for the email parameter in SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized statements/prepared statements for all user inputs, particularly the email parameter; implement strict input validation and consider WAF deployment as a defense-in-depth measure.

Recommended fix Moderate confidence

Latest stable version of Online Shopping Portal (check phpgurukul.com or github.com for v3.2 or newer)

  1. 1. Obtain the latest version of Online Shopping Portal from the official source (phpgurukul.com or github.com)
  2. 2. Backup your current database and all application files before upgrading
  3. 3. Extract the new version files to your web server document root
  4. 4. Update your database configuration in the new version to connect to your existing database
  5. 5. Run any database migration scripts provided with the new version
  6. 6. Test the login functionality at /shopping/login.php to verify the application works correctly
  7. 7. Verify that the Email parameter is now properly sanitized using prepared statements or parameterized queries
Caveat Review release notes for any configuration or database schema changes that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Online Shopping Portal Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37772 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data