Blog CmsApplication

CVE-2008-0450

HIGH · 7.5 CVSS v2.0 Published 2008-01-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Multiple PHP remote file inclusion vulnerabilities in BLOG:CMS 4.2.1.c allow remote attackers to execute arbitrary PHP code via a URL in the (1) DIR_PLUGINS parameter to (a) index.php, and the (2) DIR_LIBS parameter to (b) media.php and (c) xmlrpc/server.php in admin/.

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

Multiple remote file inclusion (RFI) vulnerabilities in BLOG:CMS 4.2.1.c allow remote attackers to execute arbitrary PHP code by supplying URLs through the DIR_PLUGINS parameter in index.php and the DIR_LIBS parameter in admin/media.php and admin/xmlrpc/server.php. The application includes files based on user-controlled input without validation, enabling remote code execution.

MitigationImplement strict input validation using whitelist-based checks to ensure included files originate from expected directories, and disable allow_url_include in PHP configuration to prevent remote file inclusion.

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
Blog CmsApplication
Affected:= 4.2.1_c

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 BLOG:CMS installation
    Search the web server document root for index.php files that contain 'BLOG:CMS' or 'blog:cm' in the source code. Typical paths include /var/www/html/, /home/*/public_html/, or C:\inetpub\wwwroot\
    Affected if BLOG:CMS software is found on the server
  2. Verify installed version
    Open the main index.php or a configuration file (such as nconfig.php or similar) in the installation directory and search for a version string. Look for '4.2.1' or '4.2.1_c' in the file contents
    Affected if The version displayed is 4.2.1_c exactly
  3. Confirm vulnerable scripts exist
    Check for the presence of admin/media.php and admin/xmlrpc/server.php files within the BLOG:CMS installation directory structure
    Affected if These admin script files exist in the installation
  4. Test parameter accessibility
    Send an HTTP GET request to index.php with a crafted DIR_PLUGINS parameter, for example: GET /index.php?DIR_PLUGINS=http://example.com/test. Similarly test admin/media.php?DIR_LIBS=http://example.com/test and admin/xmlrpc/server.php?DIR_LIBS=http://example.com/test
    Affected if The application attempts to include or resolve the URL supplied in the DIR_PLUGINS or DIR_LIBS parameter, indicating the vulnerability is present and exploitable
  5. Check PHP allow_url_include setting
    Create a PHP info file (info.php) with content '<?php phpinfo(); ?>' and access it via browser, or check php.ini directly for the allow_url_include directive value
    Affected if allow_url_include is set to On (enabled)

A server is affected if BLOG:CMS version 4.2.1_c is installed, the vulnerable script files exist, and the DIR_PLUGINS or DIR_LIBS parameters can be manipulated to include remote URLs, especially when PHP allow_url_include is enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation using whitelist-based checks to ensure included files originate from expected directories, and disable allow_url_include in PHP configuration to prevent remote file inclusion.

Fix this in Blog Cms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-0450 — 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-2008-0450 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