CVE-2006-4533
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 PHP remote file inclusion vulnerabilities in Plume CMS 1.0.6 and earlier allow remote attackers to execute arbitrary PHP code via the _PX_config[manager_path] parameter to (1) articles.php, (2) categories.php, (3) news.php, (4) prefs.php, (5) sites.php, (6) subtypes.php, (7) users.php, (8) xmedia.php, (9) frontinc/class.template.php, (10) inc/lib.text.php, (11) install/index.php, (12) install/upgrade.php, and (13) tools/htaccess/index.php. NOTE: other vectors are covered by CVE-2006-3562, CVE-2006-2645, and CVE-2006-0725.
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 confidenceMultiple PHP scripts in Plume CMS 1.0.6 and earlier contain Remote File Inclusion (RFI) vulnerabilities via the _PX_config[manager_path] parameter. Attackers can inject arbitrary PHP code by supplying a URL to a remote malicious PHP file, which gets included and executed by the vulnerable scripts.
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.6= 1.0.5CVSS 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.
-
Confirm Plume CMS installation and versionLocate the Plume CMS installation directory and check for a version file or header in the main index.php. Typical paths include /var/www/html/plume or similar web root directories. Look for a version constant or a changelog file that reveals the version number.Affected if Installed version is Plume CMS 1.0.6 or earlier, including 1.0.5
-
Identify vulnerable PHP scriptsSearch the Plume CMS installation for PHP files that reference the _PX_config[manager_path] parameter. Use grep to search for 'manager_path' within PHP files in the cms directory structure.Affected if PHP scripts that process the _PX_config[manager_path] parameter exist and are accessible via the web
-
Check PHP allow_url_fopen settingCreate a PHP info page or run php -i from command line to check the allow_url_fopen directive. In a PHPinfo page, look for the 'allow_url_fopen' value in the Core section.Affected if allow_url_fopen is enabled (On) in php.ini or php configuration
-
Verify the vulnerable parameter is reachableExamine the affected PHP scripts to confirm they accept the _PX_config[manager_path] parameter without sufficient sanitization. Check if these scripts can be accessed directly via HTTP requests without authentication.Affected if The vulnerable scripts accept the _PX_config[manager_path] parameter from user input without validation
A system is affected if Plume CMS version 1.0.6 or earlier is installed, vulnerable PHP scripts that use the _PX_config[manager_path] parameter are accessible, and PHP's allow_url_fopen is enabled, allowing remote PHP file inclusion.
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 dataUpgrade to a patched version of Plume CMS. If no update is available, disable allow_url_fopen in PHP configuration and implement strict input validation on the _PX_config[manager_path] parameter to prevent URL-based injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4533 — 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-4533 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