CVE-2004-2437
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 PHP-Fusion 4.01 allows remote attackers to execute arbitrary SQL commands via the rowstart parameter to (1) index.php or (2) members.php, or (3) the comment_id parameter to comments.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 confidenceSQL injection in PHP-Fusion 4.01 allows unauthenticated remote attackers to inject arbitrary SQL commands via the rowstart parameter in index.php and members.php, and the comment_id parameter in comments.php. The vulnerability stems from improper input validation allowing SQL operators and commands to be passed directly to the database query.
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= 4.01CVSS 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.
-
Confirm PHP-Fusion installation and versionLocate PHP-Fusion installation directory and check version.php or version info. Common paths include checking for a version file or the admin panel version display.Affected if The installed version is exactly 4.01 (PHP-Fusion Php Fusion 4.01)
-
Identify vulnerable PHP filesVerify presence of index.php, members.php, and comments.php in the web root or fusion directory.Affected if The affected files (index.php, members.php, comments.php) exist and are accessible via web requests
-
Check if rowstart parameter is usedInspect index.php and members.php source code for usage of the rowstart parameter in SQL queries without proper sanitization (check for $_GET['rowstart'] or similar).Affected if The rowstart parameter from GET request is directly used in SQL queries without escaping or parameterization
-
Check if comment_id parameter is usedInspect comments.php source code for usage of the comment_id parameter in SQL queries without proper sanitization (check for $_GET['comment_id'] or similar).Affected if The comment_id parameter from GET request is directly used in SQL queries without escaping or parameterization
-
Check PHP magic quotes configurationCheck php.ini or use phpinfo() to verify if magic_quotes_gpc is enabled. This provides partial mitigation by escaping quotes.Affected if magic_quotes_gpc is OFF and no external input sanitization is implemented in the application code
The environment is affected if PHP-Fusion version 4.01 is installed AND the vulnerable files (index.php, members.php, comments.php) use the rowstart or comment_id parameters directly in SQL queries without input validation or parameterized 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 dataUpgrade from PHP-Fusion 4.01 to a supported version with patched SQL injection vulnerabilities, or implement proper input validation and parameterized queries for all user-supplied parameters in the affected files.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-2437 — 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-2004-2437 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