CVE-2005-3160
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 · uneditedMultiple SQL injection vulnerabilities in photogallery.php in PHP-Fusion allow remote attackers to execute arbitrary SQL commands via the (1) album and (2) photo parameters.
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 vulnerabilities in PHP-Fusion's photogallery.php allow remote attackers to inject arbitrary SQL commands through the album and photo parameters, potentially exposing sensitive data or modifying database contents.
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.100= 6.00.101= 6.00.102= 6.00.103= 6.00.104= 6.00.105= 6.00.106= 6.00.107= 6.00.108= 6.00.109CVSS 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 PHP-Fusion installation and version fileSearch for PHP-Fusion's version file, typically found at includes/version.php or in the root directory. Look for a variable defining $settings['version'] or similar version constant.Affected if The installed version is 6.00.100, 6.00.101, 6.00.102, 6.00.103, 6.00.104, 6.00.105, 6.00.106, 6.00.107, 6.00.108, or 6.00.109
-
Verify photogallery.php existsLocate the photogallery.php file in the PHP-Fusion web root, commonly at /photogallery.php or /gallery/photogallery.php depending on installation structure.Affected if The file exists and is accessible via web request
-
Inspect photogallery.php for vulnerable parameter usageOpen photogallery.php and search for SQL queries that directly incorporate the 'album' or 'photo' parameters without using functions like stripinput(), sanitize(), or prepared statements.Affected if Code directly uses $_GET['album'] or $_GET['photo'] (or $_POST equivalents) in SQL queries without input sanitization or parameter binding
-
Check if gallery module is enabledIn the PHP-Fusion admin panel, verify if the Gallery/Photo Gallery module is activated, or check the database settings table for gallery_enabled status.Affected if The Gallery module is enabled and accessible to users
-
Test vulnerable parameters via HTTP requestSend a crafted request to photogallery.php with abnormal SQL characters in album or photo parameters, such as album=' OR '1'='1, and observe if SQL errors are returned or data is unexpectedly disclosed.Affected if The application returns SQL syntax errors or behaves differently than expected, indicating unsanitized input is being executed
You are affected if PHP-Fusion version is between 6.00.100 and 6.00.109 inclusive, photogallery.php exists, and the album or photo parameters are used in SQL queries without proper input sanitization 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 PHP-Fusion to a patched version or implement proper input validation and parameterized queries in photogallery.php for the album and photo parameters.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3160 — 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-3160 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