dbcve.org
Invision GalleryApplication · Invision Power Services

CVE-2006-6370

HIGH · 7.5 CVSS v2.0 Published 2006-12-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
SQL injection vulnerability in forum/modules/gallery/post.php in Invision Gallery 2.0.7 allows remote attackers to cause a denial of service and possibly have other impacts, as demonstrated using a "SELECT BENCHMARK" statement in the img parameter in a doaddcomment operation in index.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 confidence

SQL injection vulnerability in forum/modules/gallery/post.php in Invision Gallery 2.0.7 allows remote attackers to inject arbitrary SQL via the img parameter in a doaddcomment operation. The vulnerability can be exploited with SQL statements like SELECT BENCHMARK to cause denial of service or potentially extract sensitive data.

MitigationUpgrade to a patched version of Invision Gallery or implement proper input validation and parameterized queries to sanitize the img parameter before constructing SQL statements.

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
Invision GalleryApplication
Affected:= 2.0.7

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Invision Gallery is installed
    Locate the Invision Gallery installation directory on the web server. Common paths include /forum/gallery/, /gallery/, or within an Invision Power Board installation under /modules/gallery/. Check for the presence of gallery-related files and directories.
    Affected if Invision Gallery software is present on the server
  2. Identify the installed version
    Check the version.php or version information file within the Invision Gallery installation directory, or examine the main index file for a version string. Compare the discovered version against the affected version 2.0.7.
    Affected if The installed version is exactly 2.0.7
  3. Verify the vulnerable file exists
    Check for the presence of forum/modules/gallery/post.php within the Invision Gallery installation directory. This file handles the doaddcomment operation and contains the vulnerable code.
    Affected if The file post.php exists in the gallery module directory
  4. Confirm the gallery module is active
    Check the Invision Gallery configuration and module activation settings. Verify that the gallery module is enabled and accessible to users on the forum.
    Affected if The gallery module is enabled and accessible on the forum
  5. Test for SQL injection susceptibility
    If the above conditions are met, attempt a safe diagnostic request to the post.php file using the img parameter with a doaddcomment operation. For example, submit a comment request with img=1' (including a single quote) and observe if SQL syntax errors are returned in the response. This should only be done with authorization on a test system.
    Affected if SQL error messages are returned or the application behaves unexpectedly when a quote is submitted in the img parameter

You are affected if Invision Gallery version 2.0.7 is installed, the post.php file exists in the gallery module, and the gallery module is enabled, making the img parameter in doaddcomment operations vulnerable to SQL injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Invision Gallery or implement proper input validation and parameterized queries to sanitize the img parameter before constructing SQL statements.

Fix this in Invision Gallery Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-6370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-6370 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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