CVE-2026-29861
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 · uneditedPHP-MYSQL-User-Login-System v1.0 was discovered to contain a SQL injection vulnerability via the username parameter at 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 confidenceA SQL injection vulnerability exists in PHP-MYSQL-User-Login-System v1.0 where the username parameter in login.php is not properly sanitized before being used in an SQL query. An attacker can inject malicious SQL commands through the username field to manipulate database queries, potentially bypassing authentication or exfiltrating sensitive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify PHP-MYSQL-User-Login-System installationLocate the application directory and verify the presence of login.php and other application files. Check project metadata files (e.g., README, composer.json, or version file) for version identification.Affected if The application directory contains PHP-MYSQL-User-Login-System files and version is v1.0 or earlier.
-
Verify affected versionCompare your installed version against v1.0. Check any version indicators in the codebase such as version constants, readme files, or git tags.Affected if Your installed version is v1.0 or an earlier release of PHP-MYSQL-User-Login-System.
-
Examine login.php for vulnerable SQL queryOpen login.php and search for SQL query code that uses the username parameter. Look for patterns where $_POST['username'] or $_GET['username'] is directly concatenated into a SQL string without using prepared statements or binding parameters.Affected if login.php contains SQL queries that concatenate the username parameter directly into the query string.
-
Check if login functionality is exposedVerify that the login.php endpoint is accessible over the network. This can be done by accessing the login page URL or reviewing web server configuration for the application's routing.Affected if The login.php script is reachable and processes user-supplied username input.
Your environment is affected if you have PHP-MYSQL-User-Login-System v1.0 deployed with accessible login functionality where the username parameter in login.php is used in unsanitized SQL queries.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace direct string concatenation in SQL queries with prepared statements (parameterized queries) using PDO or mysqli with bound parameters. Validate and sanitize all user inputs before database operations.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-29861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-29861 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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