dbcve.org
WebcalendarApplication

CVE-2006-1537

MEDIUM · 5.0 CVSS v2.0 Published 2006-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Craig Knudsen WebCalendar 1.1.0-CVS allows remote attackers to obtain sensitive information via a direct request to (1) includes/index.php, (2) tests/add_duration_test.php, (3) tests/all_tests.php, (4) groups.php, (5) nonusers.php, (6) includes/settings.php, (7) includes/init.php, (8) includes/settings.php.orig, (9) includes/js/admin.php, (10) includes/js/edit_entry.php, (11) includes/js/edit_layer.php, (12) includes/js/export_import.php, (13) includes/js/popups.php, (14) includes/js/pref.php, or (15) includes/menu/index.php, which reveal the path in various error messages.

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

WebCalendar 1.1.0-CVS contains multiple PHP files that, when accessed directly, reveal server path information in error messages. Attackers can request files like includes/index.php, includes/init.php, tests/all_tests.php, and others to enumerate the application's directory structure, which aids in further attacks.

MitigationDeny direct web access to these files using web server access controls (e.g., .htaccess restrictions) or remove/disable unused test and include files. Configure error handlers to display generic messages instead of detailed error traces.

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
WebcalendarApplication
Affected:= 1.1.0

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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 checks

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

  1. Identify if WebCalendar is installed
    Check for WebCalendar by looking for its installation directory (commonly /webcalendar, /calendar, or similar) in your web server's document root, or search for known WebCalendar files such as index.php, login.php, or admin.php.
    Affected if WebCalendar is found in the web accessible directory.
  2. Confirm the WebCalendar version
    Locate the version file or check the main index.php for a version string. Common locations include a VERSION file, about.php, or the HTML source of the login page which may display the version.
    Affected if The installed version is 1.1.0 (specifically the 1.1.0-CVS variant).
  3. Locate vulnerable PHP files
    Check for the presence of includes/index.php, includes/init.php, and tests/all_tests.php within the WebCalendar installation directory. Use file system inspection or directory listing.
    Affected if These include or test PHP files exist in the web-accessible directory.
  4. Test direct access to vulnerable files
    Use curl or a browser to request the known vulnerable files directly via HTTP, for example: GET /webcalendar/includes/index.php. Observe any error messages or output that reveals server file paths.
    Affected if The response displays absolute server paths (such as /var/www/html/webcalendar/includes/) or detailed PHP error messages containing path information.

A user is affected if WebCalendar version 1.1.0 is installed and direct HTTP access to include or test PHP files reveals server path information in error messages.

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

Deny direct web access to these files using web server access controls (e.g., .htaccess restrictions) or remove/disable unused test and include files. Configure error handlers to display generic messages instead of detailed error traces.

Fix this in Webcalendar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-1537 — 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-1537 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