CVE-2006-6669
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 export_handler.php in WebCalendar 1.0.4 and earlier allows remote attackers to inject arbitrary web script or HTML via the format parameter.
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 confidenceReflected XSS vulnerability in WebCalendar's export_handler.php allows remote attackers to inject arbitrary JavaScript or HTML via the format parameter due to insufficient input sanitization.
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.0.4CVSS 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 WebCalendar is installedSearch your web server for files named 'export_handler.php' or look for the WebCalendar application directory (commonly in /var/www/html/webcalendar, /var/www/html/calendar, or C:\inetpub\wwwroot\webcalendar).Affected if WebCalendar application files are found on the server.
-
Identify the WebCalendar versionCheck the version.php file in the WebCalendar root directory, or look for a VERSION file, or check the main index.php for a version string.Affected if The installed version is exactly 1.0.4.
-
Verify export_handler.php existsLocate the export_handler.php file within the WebCalendar installation directory (typically in the root or includes subfolder).Affected if The file export_handler.php exists in the WebCalendar installation.
-
Check if the format parameter is processedReview the source code of export_handler.php and search for usage of the 'format' parameter (e.g., $_GET['format'] or $_POST['format']) without sanitization.Affected if The code uses the format parameter directly without input validation or encoding.
-
Test for XSS vulnerabilityIf WebCalendar is running, send a request to export_handler.php with a malicious format parameter such as: ?format=<script>alert('XSS')</script> and observe if the script executes in the response.Affected if The format parameter value is reflected unescaped in the HTML response.
You are affected if WebCalendar version 1.0.4 is installed and the export_handler.php file processes the format parameter without sanitization, allowing reflected XSS.
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 format parameter, or upgrade to a patched version of WebCalendar.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6669 — 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-6669 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