CVE-2007-3084
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 sampleblogger.php in Comdev Web Blogger 4.1 allows remote attackers to execute arbitrary PHP code via a URL in the path[docroot] parameter, a different vector than CVE-2006-5441.
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 sampleblogger.php of Comdev Web Blogger 4.1 allows remote attackers to execute arbitrary PHP code by supplying a malicious URL in the path[docroot] parameter, which gets dynamically included without proper validation.
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= 4.1CVSS 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.
-
Identify Comdev Web Blogger installationLocate the application on the web server and check for version indicators in source files, admin panels, or meta tags (commonly in header.php, index.php, or version.php within the web root or admin directory)Affected if The installed version is Comdev Web Blogger 4.1 exactly (no other versions are listed as affected)
-
Locate sampleblogger.php fileSearch the web root directory for the file sampleblogger.php (typically found in the main application directory or in a /samples/ subdirectory)Affected if The file sampleblogger.php exists and is accessible on the server - this file is required for the vulnerability to be exploitable
-
Verify dynamic inclusion of path[docroot] parameterInspect the source code of sampleblogger.php and look for include(), include_once(), require(), or require_once() statements that use the path[docroot] parameter without sanitization (e.g., include($path[docroot] . "/file.php"))Affected if The code contains dynamic include statements using the path[docroot] parameter without input validation or proper path verification
-
Confirm parameter is user-controllableTest by making a request to sampleblogger.php with an arbitrary value in the path[docroot] parameter (e.g., ?path[docroot]=http://example.com) and observe if the application attempts to include content from the supplied URLAffected if The application accepts and processes arbitrary values in the path[docroot] parameter without rejecting remote URLs or invalid paths
You are affected if you have Comdev Web Blogger version 4.1 installed with the sampleblogger.php file present and accessible, and the application allows the path[docroot] parameter to control which file gets included dynamically.
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 dataRemove or disable the vulnerable sampleblogger.php file, or apply available vendor patches; additionally, disable allow_url_include in PHP configuration and implement proper input validation on the path[docroot] parameter.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3084 — 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-2007-3084 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