CVE-2006-1013
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 include vulnerability in index.php in SMartBlog (aka SMBlog) 1.2 allows remote attackers to include and execute arbitrary PHP files via (1) the pg parameter and (2) a query string without a 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 (RFI) vulnerability in SMartBlog 1.2 index.php allows attackers to control the pg parameter or use a bare query string to include and execute arbitrary PHP files from remote locations, leading to complete system compromise.
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.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
- 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 Smartblog installation and versionLook for the Smartblog directory on your web server and check for version identifiers in files such as version.php, about.php, or README files within the Smartblog installation directory.Affected if Smartblog version 1.2 is installed on the server.
-
Locate the vulnerable index.php fileSearch for index.php within the Smartblog installation directory and verify its presence.Affected if The file /path/to/smartblog/index.php exists on the server.
-
Inspect the pg parameter handling in index.phpOpen index.php and search for code that uses the 'pg' parameter in include, require, or similar file inclusion functions without proper sanitization.Affected if The code directly uses $_GET['pg'] or $_REQUEST['pg'] in include/require statements without validation.
-
Check for bare query string RFI vectorReview index.php to see if the code processes the query string directly (e.g., using include without any parameter) which could allow arbitrary URL injection.Affected if The code includes files based on raw query string parameters without validation.
-
Verify PHP allow_url_include settingCheck the PHP configuration file (php.ini) or run phpinfo() to check if allow_url_include is enabled.Affected if allow_url_include is set to On in PHP configuration, allowing remote URLs to be included.
Your environment is affected if Smartblog version 1.2 is installed and the index.php file contains vulnerable code that uses the pg parameter or raw query string in file inclusion functions without input 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 dataSanitize and validate all user-supplied input before use in file inclusion functions. Implement whitelist-based validation for the pg parameter, disable allow_url_include in PHP configuration, and refactor code to use static file paths instead of user-controlled variables.
- 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-1013 — 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-1013 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