CVE-2006-1922
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 · uneditedPHP remote file inclusion vulnerability in (1) about.php or (2) auth.php in TotalCalendar allows remote attackers to execute arbitrary PHP code via a URL in the inc_dir 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 confidenceRemote file inclusion vulnerability in TotalCalendar's about.php and auth.php scripts allows arbitrary PHP code execution through the inc_dir parameter, which is directly used in include/require statements without proper validation, enabling attackers to include malicious remote files.
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= 2.0= 2.1= 2.2CVSS 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
- None
AV:N/AC:L/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.
-
Identify TotalCalendar installation and versionSearch your web root for TotalCalendar directories and check version.php or any version file for version 2.0, 2.1, or 2.2Affected if TotalCalendar version is 2.0, 2.1, or 2.2
-
Locate vulnerable script about.phpFind the file 'about.php' within your TotalCalendar installation and verify it contains an include or require statement using the 'inc_dir' parameterAffected if about.php exists and uses inc_dir in include/require without validation
-
Locate vulnerable script auth.phpFind the file 'auth.php' within your TotalCalendar installation and verify it contains an include or require statement using the 'inc_dir' parameterAffected if auth.php exists and uses inc_dir in include/require without validation
-
Check PHP allow_url_include settingCheck your php.ini or run 'php -i' or 'ini_get("allow_url_include")' to see if remote file inclusion is enabledAffected if allow_url_include is set to On or 1 in PHP configuration
Your environment is affected if you have TotalCalendar version 2.0, 2.1, or 2.2 installed with the vulnerable about.php or auth.php scripts present and the inc_dir parameter is passed without validation, especially if allow_url_include is enabled in PHP.
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 strict input validation on the inc_dir parameter using a whitelist approach, or better yet, remove the parameter entirely and use hardcoded include paths. Ensure all include/require statements use absolute paths and disable allow_url_include in PHP configuration.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1922 — 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-1922 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