BolinosApplication

CVE-2006-4851

HIGH · 7.5 CVSS v2.0 Published 2006-09-19
Fix available
A fix is available. Upgrade to after 4.5.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
PHP remote file inclusion vulnerability in system/_b/contentFiles/gBHTMLEditor.php in BolinOS 4.5.5 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the gBRootPath parameter. NOTE: the provenance of this information is unknown; the details are obtained from third party information.

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 · moderate confidence

Remote file inclusion vulnerability in BolinOS 4.5.5 and earlier allows arbitrary PHP code execution through the gBRootPath parameter in system/_b/contentFiles/gBHTMLEditor.php. Attackers can supply a malicious URL that the PHP include() or require() function will execute, effectively giving them remote code execution on the server.

MitigationUpgrade BolinOS to a version beyond 4.5.5 that includes security patches, or disable/remove the vulnerable gBHTMLEditor.php component entirely if no upgrade path exists. Implement WAF rules to block URL parameters in requests to this endpoint as an interim measure.

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
BolinosApplication
Affected:<= 4.5.5= 4.3.0= 4.4.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm BolinOS installation
    Identify if BolinOS web application is installed by checking for characteristic files, directories, or HTTP response headers (e.g., look for 'bolinos', 'BolinOS', or the typical directory structure).
    Affected if BolinOS is present on the server.
  2. Determine BolinOS version
    Locate the installed version by examining version files, changelogs, or the main index/header files that may contain version strings like '4.5.5', '4.4.1', or '4.3.0'. Compare against the affected ranges: <= 4.5.5, specifically 4.3.0, 4.4.1, and earlier versions.
    Affected if The installed version is 4.5.5 or earlier (including 4.3.0 and 4.4.1).
  3. Verify vulnerable file exists
    Check for the presence of the file system/_b/contentFiles/gBHTMLEditor.php in the web root or application directory.
    Affected if The file gBHTMLEditor.php exists on the system.
  4. Inspect the vulnerable code
    Examine the source code of gBHTMLEditor.php to confirm it uses the gBRootPath parameter in an include() or require() statement without proper sanitization.
    Affected if The code contains an include() or require() call using the gBRootPath parameter without input validation.
  5. Test parameter accessibility
    Attempt a harmless test request to the endpoint (e.g., GET /system/_b/contentFiles/gBHTMLEditor.php?gBRootPath=test) to verify the parameter is processed and the file is reachable via HTTP.
    Affected if The server processes the gBRootPath parameter and the file is accessible over HTTP.

A user is affected if BolinOS version 4.5.5 or earlier is installed AND the file system/_b/contentFiles/gBHTMLEditor.php exists AND the gBRootPath parameter is processed by the application without validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 4.5.5
Interim mitigation

Upgrade BolinOS to a version beyond 4.5.5 that includes security patches, or disable/remove the vulnerable gBHTMLEditor.php component entirely if no upgrade path exists. Implement WAF rules to block URL parameters in requests to this endpoint as an interim measure.

Fix this in Bolinos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-4851 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-4851 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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