dbcve.org
Bookmark4uApplication · Sangwan Kim

CVE-2006-2877

HIGH · 7.5 CVSS v2.0 Published 2006-06-07
Fix available
A fix is available. Upgrade to after 2.0 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 Bookmark4U 2.0.0 and earlier allows remote attackers to include arbitrary PHP files via the include_prefix parameter in (1) inc/dbase.php, (2) inc/config.php, (3) inc/common.php, and (4) inc/function.php. NOTE: it has been reported that the inc directory is protected by a .htaccess file, so this issue only applies in certain environments or configurations.

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 confidence

Bookmark4U 2.0.0 and earlier contains a PHP remote file inclusion vulnerability where the include_prefix parameter in inc/dbase.php, inc/config.php, inc/common.php, and inc/function.php allows attackers to include arbitrary PHP files from remote sources, leading to potential code execution.

MitigationRemediate by implementing strict input validation on the include_prefix parameter (e.g., whitelist allowed values, disable allow_url_include), or upgrade to a patched version if available. The .htaccess protection noted may need review to ensure it's effective in the deployment environment.

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
Bookmark4uApplication
Affected:<= 2.0

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. Locate Bookmark4U installation
    Search the web server document root for directories containing 'bookmark4u', 'bookmark', or 'bookmark4U' (case-insensitive). Common paths: /var/www/html/bookmark4u, /home/*/public_html/bookmark4u, or C:\inetpub\wwwroot\bookmark4u
    Affected if Bookmark4U is found on the server
  2. Identify Bookmark4U version
    Open any version file such as version.php, readme.txt, or index.php in the Bookmark4U directory and search for a version string (e.g., '2.0.0', '1.9', '1.5'). Check the main index.php or a dedicated version file for the version number
    Affected if The installed version is 2.0.0 or earlier (any version <= 2.0)
  3. Verify vulnerable PHP files exist
    Check for the existence of these files within the Bookmark4U inc/ directory: dbase.php, config.php, common.php, and function.php. List the contents of the inc/ folder to confirm
    Affected if All four files (inc/dbase.php, inc/config.php, inc/common.php, inc/function.php) exist in the installation
  4. Confirm include_prefix parameter usage
    Open each vulnerable file (inc/dbase.php, inc/config.php, inc/common.php, inc/function.php) and search for 'include_prefix' or 'include' statements that use this parameter, e.g., 'include($include_prefix . ...)' or 'include_once($include_prefix . ...)'
    Affected if The code contains include/require statements using the include_prefix parameter without sanitization
  5. Check PHP allow_url_include setting
    Create a PHP file with '<?php phpinfo(); ?>' and access it via the web server, or run 'php -i' from command line. Look for the 'allow_url_include' directive in the output
    Affected if allow_url_include is enabled (On) in php.ini or PHP configuration

A user is affected if Bookmark4U version 2.0 or earlier is installed with the vulnerable inc/ files present and allow_url_include is enabled in PHP, allowing remote file inclusion via the include_prefix parameter.

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 2.0
Interim mitigation

Remediate by implementing strict input validation on the include_prefix parameter (e.g., whitelist allowed values, disable allow_url_include), or upgrade to a patched version if available. The .htaccess protection noted may need review to ensure it's effective in the deployment environment.

Fix this in Bookmark4u Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-2877 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2877 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