CVE-2009-0709
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 · uneditedSQL injection vulnerability in login.php in PHPFootball 1.6 allows remote attackers to execute arbitrary SQL commands via the user parameter. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 PHPFootball 1.6's login.php allows remote attackers to execute arbitrary SQL commands via the user parameter. This is a classic SQL injection flaw where user input is directly concatenated into SQL queries without proper sanitization or parameterized queries.
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= 1.6CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Locate PHPFootball installationSearch for the login.php file in your web server's document root. Common paths include /var/www/html/phpfootball/, /www/phpfootball/, or similar web-accessible directories. Check for a file named login.php that belongs to the PHPFootball application.Affected if login.php from PHPFootball version 1.6 exists in your web accessible directories
-
Identify installed versionCheck for a version file, README, or footer/includes within the PHPFootball installation. Look for version indicators in comments within login.php or in files like version.php, config.php, or a changelog. Compare the version number to 1.6.Affected if The installed PHPFootball version is exactly 1.6
-
Examine login.php for vulnerable code patternOpen login.php and search for SQL query patterns that concatenate the 'user' parameter directly into WHERE clauses. Look for code resembling: $query = "SELECT * FROM users WHERE user='" . $_POST['user'] . "'" or similar unsanitized user input in SQL statements.Affected if login.php contains SQL queries that directly concatenate the user parameter without sanitization, prepared statements, or parameterized queries
-
Verify user input flows to SQL without escapingTrace the code path from $_POST['user'] or $_GET['user'] in login.php through to the SQL query execution. Confirm no mysql_real_escape_string, htmlspecialchars, prepared statements, or input validation functions are applied before the user value is used in the query.Affected if User input from the user parameter reaches SQL query execution without any escaping or parameterization
You are affected if PHPFootball version 1.6 is installed and its login.php contains SQL queries that directly concatenate the user parameter into the query without sanitization or prepared statements.
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 in login.php, validating and escaping all user input before incorporating it into database queries.
- 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-2009-0709 — 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-2009-0709 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