CVE-2006-1660
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 · uneditedCross-site scripting (XSS) vulnerability in image_desc.php in Softbiz Image Gallery allows remote attackers to inject arbitrary web script or HTML via msg parameter. NOTE: the provenance of this information is unknown; the details are obtained 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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability exists in the image_desc.php script of Softbiz Image Gallery. The msg parameter accepts user-supplied input and reflects it back into the HTML output without proper sanitization or output encoding, allowing attackers to inject arbitrary JavaScript or HTML.
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 dataall versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 Softbiz Image Gallery installationLocate the web application directory - typically look for folders named 'sb' or 'softbiz' or check your web server document root for image_gallery or similar gallery-related directoriesAffected if The software is present on the server
-
Identify vulnerable script locationSearch for the image_desc.php file within the gallery installation directory - common paths include /image_gallery/image_desc.php, /gallery/image_desc.php, or /sb/image_desc.phpAffected if image_desc.php exists in the gallery installation
-
Check if msg parameter is in useReview the image_desc.php source code and search for usage of the 'msg' parameter (typically via $_GET['msg'] or similar request variable) that gets output to HTMLAffected if The script uses the msg parameter from user input without validation
-
Verify output encoding is missingIn image_desc.php, examine where the msg parameter value is output - look for lines that echo or print the parameter directly without htmlspecialchars() or equivalent encodingAffected if The msg parameter is reflected in HTML output without htmlspecialchars() or proper encoding functions
-
Confirm the vulnerable code path is reachableTest that image_desc.php is accessible via HTTP/HTTPS and accepts the msg parameter in the URL query string (e.g., image_desc.php?msg=test)Affected if The script accepts and reflects the msg parameter to the user without sanitization
You are affected if Softbiz Image Gallery is installed and the image_desc.php script reflects the msg parameter in HTML output without using htmlspecialchars() or equivalent output encoding.
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 dataImplement proper input validation and output encoding on the msg parameter in image_desc.php. All user-supplied input should be sanitized using htmlspecialchars() or equivalent encoding functions before being output in HTML context.
- 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-2006-1660 — 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-2006-1660 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