dbcve.org
MyblogApplication · Sam Crew

CVE-2007-1990

HIGH · 7.5 CVSS v2.0 Published 2007-04-12
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
PHP remote file inclusion vulnerability in games.php in Sam Crew MyBlog, possibly 1.0 through 1.6, allows remote attackers to execute arbitrary PHP code via a URL in the id parameter, a different vector than CVE-2007-1968. NOTE: the provenance of this information is unknown; the details are obtained solely 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 · low confidence

PHP remote file inclusion vulnerability in games.php of Sam Crew MyBlog (versions 1.0-1.6) allows remote attackers to execute arbitrary PHP code via a URL in the id parameter. This enables attackers to include malicious remote files, leading to arbitrary code execution on the server.

MitigationDisable PHP's allow_url_fopen and allow_url_include settings; implement strict input validation on the id parameter to reject URL-based values; validate all include/require paths against an allowlist of permitted 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
MyblogApplication
Affected:= 1.0= 1.1= 1.2= 1.3= 1.4= 1.5= 1.6

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 Sam Crew MyBlog installation and version
    Locate the MyBlog installation directory and check for version information in files such as version.php, index.php, or a README file. Common paths include /myblog/, /blog/, or / on the web server.
    Affected if The installed version is 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, or 1.6
  2. Verify games.php exists in the web root
    Check for the presence of games.php in the MyBlog installation directory. Look in the main application folder accessible via the web server.
    Affected if The file games.php exists and is accessible via the web server
  3. Inspect the id parameter usage in games.php
    Open games.php and search for code that uses the id parameter in include(), require(), include_once(), or require_once() functions without validation. Look for patterns like include($_GET['id']) or similar.
    Affected if The id parameter is used in an include/require statement without input sanitization or allowlist validation
  4. Check PHP runtime configuration for remote file inclusion support
    Review php.ini or use phpinfo() to check if allow_url_fopen and allow_url_include are enabled. These settings control whether PHP can include files from remote URLs.
    Affected if allow_url_fopen or allow_url_include is set to On (enabled)
  5. Test for vulnerability exposure
    Attempt a controlled test by requesting games.php?id=http://example.com/ (replacing example.com with a controlled test endpoint) and observe if PHP attempts to fetch the remote URL.
    Affected if The server attempts to fetch or include the remote URL, indicating the vulnerability is exploitable

The environment is affected if Sam Crew MyBlog versions 1.0-1.6 is installed, games.php is accessible, the id parameter is used in an unsafe include/require, and PHP allows remote URL inclusion.

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

Disable PHP's allow_url_fopen and allow_url_include settings; implement strict input validation on the id parameter to reject URL-based values; validate all include/require paths against an allowlist of permitted files.

Fix this in Myblog Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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