CVE-2006-6081
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 Smarty_Compiler.class.php in Telaen 1.1.0 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the plugin_file 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 Telaen 1.1.0 and earlier allows arbitrary PHP code execution through the Smarty_Compiler.class.php plugin_file parameter, which accepts unsanitized user input enabling inclusion of remote malicious PHP 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<= 1.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
- 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.
-
Locate Telaen installationSearch for Telaen files on the system. Look for directories containing 'telaen' in web server document roots (e.g., /var/www/, /htdocs/, C:\inetpub\wwwroot\). Common paths include /telaen/ or /webmail/telaen/. Check for files like index.php, Telaen.php, or the Smarty_Compiler.class.php file.Affected if Telaen is not installed on the system, then the vulnerability does not apply.
-
Determine installed Telaen versionOpen the main Telaen PHP file (such as index.php, Telaen.php, or version.php) and look for a version string. Search for patterns like 'version', '$version', or 'VERSION' followed by a numeric value (e.g., '1.1.0', '1.0.x').Affected if The installed version is 1.1.0 or any earlier version (e.g., 1.0.x), placing it within the affected range.
-
Verify Smarty_Compiler.class.php existsLocate the Smarty_Compiler.class.php file within the Telaen installation directory. This file is typically found in a lib/, include/, or smarty/ subdirectory under the Telaen root.Affected if The file exists and contains the vulnerable plugin_file parameter handling code, indicating the attack surface is present.
-
Check PHP allow_url settingsCreate a PHP script with '<?php phpinfo(); ?>' and access it through the web server, or run 'php -i' from command line. Look for the 'allow_url_fopen' and 'allow_url_include' settings in the PHP configuration section.Affected if Either allow_url_fopen or allow_url_include is enabled (set to On), which permits the inclusion of remote URLs required for this RFI exploit to function.
A user is affected if Telaen version 1.1.0 or earlier is installed, the Smarty_Compiler.class.php file is present, and PHP's allow_url_fopen or allow_url_include is enabled, allowing remote file inclusion via the plugin_file parameter.
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 dataDisable PHP's allow_url_fopen and allow_url_include settings, and implement strict input validation on the plugin_file parameter to reject URLs or paths outside expected directories.
- 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-6081 — 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-6081 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