CVE-2006-3359
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 index.php in NewsPHP 2006 PRO allow remote attackers to inject arbitrary web script or HTML via the (1) words, (2) id, (3) topmenuitem, and (4) cat_id parameters in (a) index.php; and the (5) category parameter in (b) inc/rss_feed.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 confidenceMultiple SQL injection vulnerabilities in NewsPHP 2006 PRO allow remote attackers to inject arbitrary SQL commands via unsanitized user input in parameters (words, id, topmenuitem, cat_id) in index.php and (category) in inc/rss_feed.php. The application fails to properly validate or sanitize these parameters before using them 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= 2006_proCVSS 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 NewsPHP versionLocate the version identifier in the NewsPHP installation - check the main index.php file header, a README file, or any version.php file for the exact version string (look for '2006_pro' or similar)Affected if The installed version is NewsPHP 2006 PRO (exactly version 2006_pro)
-
Verify vulnerable file index.php existsCheck for the presence of index.php in the web root directoryAffected if index.php exists and is part of the active NewsPHP installation
-
Verify vulnerable file inc/rss_feed.php existsCheck for the presence of inc/rss_feed.php in the installationAffected if inc/rss_feed.php exists in the NewsPHP installation directory
-
Inspect index.php for vulnerable parameter handlingOpen index.php and search for direct use of parameters 'words', 'id', 'topmenuitem', or 'cat_id' in SQL query strings without visible sanitization functions (such as prepared statements, escaping functions, or validation routines)Affected if Any of these four parameters are used in SQL queries without proper sanitization/parameterization
-
Inspect inc/rss_feed.php for vulnerable parameter handlingOpen inc/rss_feed.php and search for direct use of the 'category' parameter in SQL query strings without visible sanitization functionsAffected if The 'category' parameter is used in SQL queries without proper sanitization/parameterization
A system is affected if it runs NewsPHP version 2006_pro AND contains either index.php or inc/rss_feed.php with the specified parameters being used in SQL queries without input 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 dataImplement prepared statements/parameterized queries for all database operations, or alternatively apply comprehensive input validation and escaping for all user-supplied parameters before constructing SQL queries. The fix must cover all five vulnerable parameters across both files.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3359 — 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-3359 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