CVE-2006-2678
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 cross-site scripting (XSS) vulnerabilities in Pre News Manager 1.0 allow remote attackers to inject arbitrary web script or HTML via the (1) id parameter to (a) index.php, and the (2) nid parameter to (b) news_detail.php, (c) email_story.php, (d) thankyou.php, (e) printable_view.php, (f) tella_friend.php, and (g) send_comments.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 confidencePre News Manager 1.0 contains multiple cross-site scripting vulnerabilities where the id parameter in index.php and the nid parameter in seven different PHP files (news_detail.php, email_story.php, thankyou.php, printable_view.php, tella_friend.php, and send_comments.php) accept user-supplied input without proper sanitization or output encoding, allowing injection of arbitrary HTML or JavaScript.
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= 1.0CVSS 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
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
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 Pre News Manager installationSearch the web server for the presence of Pre News Manager by locating the index.php file in the web root or checking for the directory containing 'pre news manager' files.Affected if Pre News Manager is installed on the server
-
Verify the version is 1.0Check the application version by examining the README, version file, or any metadata within the Pre News Manager files that indicate the software version.Affected if The installed version is Pre News Manager 1.0
-
Locate vulnerable PHP filesIdentify the presence of index.php, news_detail.php, email_story.php, thankyou.php, printable_view.php, tella_friend.php, and send_comments.php within the Pre News Manager installation directory.Affected if Any of these seven PHP files plus index.php exist in the installation
-
Check if id or nid parameters are processedExamine the source code of index.php for handling of the 'id' parameter, and examine news_detail.php, email_story.php, thankyou.php, printable_view.php, tella_friend.php, and send_comments.php for handling of the 'nid' parameter. Look for direct usage of these parameters in HTML output without visible sanitization functions.Affected if The code processes id or nid parameters and reflects them in HTML output without apparent sanitization or encoding
The environment is affected if Pre News Manager version 1.0 is installed and the vulnerable PHP files process id or nid parameters 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 dataImplement input validation and output encoding for all user-supplied parameters, particularly id and nid. Use context-appropriate encoding when reflecting data in HTML output, and consider deploying a web application firewall as a temporary defense-in-depth measure.
- 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-2006-2678 — 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-2678 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