CVE-2026-5646
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 · uneditedA security vulnerability has been detected in code-projects Easy Blog Site 1.0. Affected by this issue is some unknown functionality of the file login.php. The manipulation of the argument username/password leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used.
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 · moderate confidenceSQL injection vulnerability in code-projects Easy Blog Site 1.0 login.php file. The username and password parameters are not properly sanitized, allowing attackers to inject malicious SQL queries. This is a pre-authentication vulnerability exploitable remotely.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm Easy Blog Site 1.0 is installedSearch the webroot for files containing 'Easy Blog Site' branding or check application documentation to identify the installed product and version.Affected if The software is code-projects Easy Blog Site version 1.0
-
Locate the login.php fileSearch the web server document root for login.php, typically found in the application root or /admin directory.Affected if The login.php file exists in the application
-
Inspect the SQL query implementation in login.phpOpen login.php in a text editor or use 'grep' to search for SQL query strings. Look for dynamic SQL construction using variables like $username or $password concatenated directly into the query.Affected if The code contains unsanitized SQL queries with user input (username/password) passed directly without parameterized queries or input sanitization
-
Check for prepared statements or input sanitizationSearch the login.php file for functions like 'mysqli_prepare', 'PDO::prepare', 'mysql_real_escape_string', or any input validation routines applied to the username and password variables.Affected if No prepared statements or escape functions are used for the login SQL queries
-
Verify network exposure of the login pageAccess the login.php URL from a browser or use curl to confirm the page is reachable externally (e.g., http://target/login.php).Affected if The login page is accessible over the network without authentication
A user is affected if they have code-projects Easy Blog Site version 1.0 running and the login.php file contains unsanitized SQL queries using username/password parameters.
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 dynamic SQL queries with parameterized queries (prepared statements) in login.php. Apply input validation and employ least-privilege database accounts. Consider a WAF as a temporary compensating control.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5646 — 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-5646 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