Bsq SitestatsApplication · Joomla
CVE-2006-4995
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 BSQ Sitestats (bsq_sitestats) before 2.1.1 for Joomla! allows remote attackers to execute arbitrary PHP code via a URL in the mosConfig_absolute_path 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 BSQ Sitestats component for Joomla! allows remote attackers to execute arbitrary PHP code via the mosConfig_absolute_path parameter, enabling complete system compromise through inclusion of malicious remote 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
Bsq SitestatsApplication
= 2.1.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 if BSQ Sitestats component is installedCheck for the presence of the BSQ Sitestats component directory in the Joomla installation, typically found at /components/com_bsq_sitestats/ or search for files containing 'bsq_sitestats' in the components folderAffected if The component directory exists on the server
-
Determine the installed version of BSQ SitestatsExamine the component's version file, manifest XML, or any version.php file within the BSQ Sitestats component directory. Common locations include /components/com_bsq_sitestats/bsqSitestats.xml or a version.php file within the component folderAffected if The version is exactly 2.1.1 (as indicated by = 2.1.1 in the affected versions)
-
Inspect the component for vulnerable include statementsReview the PHP files in the BSQ Sitestats component for usage of the mosConfig_absolute_path variable in include, require, or similar statements. Search for patterns like 'include($mosConfig_absolute_path' or 'require($mosConfig_absolute_path'Affected if The code uses mosConfig_absolute_path in dynamic file inclusion without sanitization
-
Test for exposed mosConfig_absolute_path parameterAttempt a controlled test by submitting a GET or POST request to any BSQ Sitestats component file with a test value for mosConfig_absolute_path (e.g., ?mosConfig_absolute_path=http://example.com) and observe if the application attempts to include the supplied valueAffected if The application processes the mosConfig_absolute_path parameter without validation
-
Check for signs of compromise or malicious inclusionsReview web server access logs and application logs for requests to BSQ Sitestats URLs containing suspicious values in mosConfig_absolute_path, such as remote URLs, common web shell patterns, or base64-encoded commandsAffected if Historical or current log entries show attempts to exploit this RFI vulnerability
The system is affected if BSQ Sitestats version 2.1.1 is installed and the component uses the mosConfig_absolute_path parameter in dynamic file inclusions 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 to BSQ Sitestats version 2.1.1 or later, or implement proper input validation/sanitization on the mosConfig_absolute_path parameter to prevent arbitrary file inclusion.
Fix this in Bsq Sitestats
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4995 — 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-4995 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