CVE-2005-4517
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 6.00.200 through 6.00.300 allows remote attackers to execute arbitrary SQL commands via the ratings parameter in multiple scripts, such as ratings_include.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 vulnerability in PHP-Fusion versions 6.00.200 through 6.00.300 allows remote attackers to execute arbitrary SQL commands via the ratings parameter in multiple scripts including ratings_include.php. User-supplied input is not properly sanitized before being used in SQL 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= 6.00.200= 6.00.206= 6.00.207= 6.00.300CVSS 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 installationCheck for the presence of PHP-Fusion by looking for characteristic files such as admin panels, infusion directories, or the main configuration file in the web root. Also check for the PHP-Fusion copyright or branding in page footers.Affected if PHP-Fusion CMS is installed on the server
-
Identify PHP-Fusion versionLocate the version information file, typically in the root directory (version file or config). Common locations include a version.php file or the main config file. Open and read the version string.Affected if The installed version matches 6.00.200, 6.00.206, 6.00.207, 6.00.300, or any version in the range 6.00.200 through 6.00.300
-
Locate vulnerable ratings_include.phpSearch the web root directory for the file ratings_include.php. This file is typically located in the includes or ratings folder of the PHP-Fusion installation.Affected if The file ratings_include.php exists in the PHP-Fusion installation directory
-
Verify ratings parameter handlingExamine the ratings_include.php file source code. Look for SQL queries that incorporate the ratings parameter without proper sanitization functions such as mysql_real_escape_string, or use of prepared statements.Affected if The ratings parameter is used directly in SQL queries without escaping or parameterization
A user is affected if they have PHP-Fusion versions 6.00.200 through 6.00.300 installed with the ratings_include.php file present and the ratings parameter processed in SQL queries without sanitization.
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 dataUpdate PHP-Fusion to the latest patched version. If no update is available, implement proper input validation and convert all SQL queries in affected scripts to use parameterized queries/prepared statements.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4517 — 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-2005-4517 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