dbcve.org
Php Mysql User Signup Login SystemDatabase / datastore · Keerti1924

CVE-2024-2264

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A vulnerability, which was classified as critical, has been found in keerti1924 PHP-MYSQL-User-Login-System 1.0. Affected by this issue is some unknown functionality of the file /login.php. The manipulation of the argument email leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-256034 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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

A critical SQL injection vulnerability exists in the login.php file of PHP-MYSQL-User-Login-System 1.0. The email parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code. The exploit is publicly available, increasing urgency for remediation.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) using PDO or mysqli, ensuring all user input is treated as data rather than SQL code. Validate and sanitize the email parameter as a secondary defense layer.

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
Php Mysql User Signup Login SystemDatabase / datastore
Affected:= 1.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the login.php file
    Search the web server document root for a file named 'login.php' from a PHP-MYSQL-User-Login-System. Common paths include /var/www/html/, /www/, or the application's root directory.
    Affected if The login.php file from Keerti1924 Php Mysql User Signup Login System version 1.0 is found on the server
  2. Verify the product version
    Check for a version.php, README, or any version indicator in the application directory. Compare against the affected version: 1.0
    Affected if The installed version is exactly 1.0 of Keerti1924 Php Mysql User Signup Login System
  3. Inspect the email parameter handling in login.php
    Open login.php and locate the code handling the 'email' POST or GET parameter. Look for how this parameter is retrieved and used in SQL queries.
    Affected if The email parameter is used directly in SQL queries without apparent sanitization or parameterization
  4. Check for unsafe SQL query construction
    Search in login.php for SQL query strings (SELECT, INSERT, UPDATE, DELETE) that concatenate the email variable directly, for example: "SELECT * FROM users WHERE email='" . $email . "'". Also check for mysql_query or mysqli_query calls where the email variable is embedded in the query string.
    Affected if The SQL query containing the email parameter is constructed using string concatenation or interpolation rather than prepared statements or parameter binding

You are affected if you have Keerti1924 Php Mysql User Signup Login System version 1.0 installed with a login.php file that 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries (prepared statements) using PDO or mysqli, ensuring all user input is treated as data rather than SQL code. Validate and sanitize the email parameter as a secondary defense layer.

Fix this in Php Mysql User Signup Login System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2264 — 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-2024-2264 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