Safeguard
Vulnerability Analysis•

CVE-2024-0651: Medium SQL Injection in PHPGurukul Visitor System

CVE-2024-0651 is a medium SQL Injection flaw in PHPGurukul Company Visitor Management System. Apply the vendor fix or restrict access. Check now.

Safeguard Security Team
3 min read

CVE-2024-0651 is a medium severity SQL Injection flaw in PHPGurukul Company Visitor Management System, scored CVSS 6.3. The record lists PHPGurukul Company Visitor Management System 1.0. The record names no fixed version. Use the steps below to confirm your exposure and plan the fix.

What's affected

The record lists PHPGurukul Company Visitor Management System 1.0. The affected file is search-visitor.php.

The CVSS vector in the record is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, with a base score of 6.3 (Medium). KEV status: not listed in the record.

Fixed version: The record names no fixed version. Check the PHPGurukul site for updates.

Where sources differ: The VulDB description calls the issue critical, while the CVSS score in the record is 6.3, which is Medium.

How to check if you're exposed

Find the installed version in the product admin area, its version file, or your deployment manifest, and compare it with the record. Review web server access logs for unexpected requests to the affected path, and check whether the admin or affected component is reachable from the internet.

What to do now

  1. Find every deployment of the affected product and its version.
  2. Apply the vendor fix if one exists. If the vendor has not responded, consider removing the product or placing it behind a web application firewall and an IP allow list.
  3. Block or monitor requests to the affected path, and review logs for earlier abuse.
  4. Restrict the admin area to a trusted network.

Why it matters

CWE-89 describes this class. SQL injection happens when input is placed into a database query without being separated from the query text. The database then treats part of the input as instructions, which can expose, change or delete data the page was never meant to reach. The standard cure is parameterized queries plus least privilege for the database account the application uses.

The record notes that an exploit has been disclosed publicly, which shortens the time between disclosure and scanning by others. The record does not say the flaw is exploited in the wild, and it is not in the CISA KEV catalog.

For a wider view, a free in-browser dependency scan and the Gold directory show where PHPGurukul Company Visitor Management System sits in your software, and reachability analysis helps separate code that can actually be hit from code that merely ships.

Quick check

Is CVE-2024-0651 exploited in the wild?

The record's KEV flag is false, and none of the pages I fetched said otherwise. That is not proof of safety, so still patch or restrict access.

What if no fix exists?

Restrict the affected path and the admin area to trusted networks, and consider replacing the product.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.