CVE-2009-0970
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 includes/class_image.php in PHP Pro Bid 6.05, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the fileExtension parameter. 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 · moderate confidenceRemote File Inclusion vulnerability in PHP Pro Bid 6.05's includes/class_image.php allows execution of arbitrary PHP code through the fileExtension parameter when register_globals is enabled. An attacker can supply a malicious URL to this parameter, causing the application to include and execute remote PHP code.
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= 6.05CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 PHP Pro Bid versionLook for a version file (such as version.php, or check the admin panel for version info) or inspect the source code for a version constant. Common locations include a version.php file in the root or includes directory, or a meta tag in the header.Affected if The installed version is exactly 6.05 or falls within the 6.05 branch.
-
Locate the vulnerable scriptCheck if the file includes/class_image.php exists in the web root. This file handles image processing and contains the fileExtension parameter handling.Affected if The file includes/class_image.php is present on the server.
-
Verify register_globals is enabledCreate a PHP info page (<?php phpinfo(); ?>) and access it via browser, or check the php.ini configuration file for 'register_globals = On'. Alternatively, check if the get_defined_vars() function shows variables that should not be defined by default.Affected if register_globals is set to On in php.ini or phpinfo() shows it as enabled.
-
Test for the vulnerable parameterInspect the class_image.php source code around the fileExtension parameter handling. Look for code that uses this parameter in an include or require statement without proper sanitization. The vulnerable code typically uses the parameter directly in an include() call.Affected if The code in class_image.php uses the fileExtension parameter in an include/require statement without validation, and register_globals can inject values into this parameter.
The environment is affected if PHP Pro Bid version 6.05 is installed, the file includes/class_image.php exists, and register_globals is enabled in PHP configuration.
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 dataDisable register_globals in php.ini (or upgrade to PHP 5.4+ where it's removed), and upgrade PHP Pro Bid to a current version if available.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0970 — 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-2009-0970 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