dbcve.org
PHPApplication

CVE-2007-0909

HIGH · 7.5 CVSS v2.0 Published 2007-02-13
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 format string vulnerabilities in PHP before 5.2.1 might allow attackers to execute arbitrary code via format string specifiers to (1) all of the *print functions on 64-bit systems, and (2) the odbc_result_all function.

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

Format string vulnerabilities in PHP before 5.2.1 allow attackers to inject format string specifiers (like %s, %x) into *print functions on 64-bit systems and the odbc_result_all function. This can lead to arbitrary code execution by manipulating format string parameters.

MitigationUpgrade PHP to version 5.2.1 or later. If unable to upgrade immediately, audit code for direct use of user input in printf-style functions and sanitize all inputs before passing to these functions.

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
PHPApplication
Affected:= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.0.6= 3.0.7= 3.0.8= 3.0.9= 3.0.10= 3.0.11
Secure LinuxOperating system
Affected:= 2.2= 3.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. Check installed PHP version
    Run `php -v` or `phpinfo()` to identify the PHP version
    Affected if Version is earlier than 5.2.1 (includes all 3.x, 4.x, and early 5.x versions)
  2. Identify system architecture
    Run `uname -m` or `getconf LONG_BIT` to determine if the system is 64-bit
    Affected if System is 64-bit and PHP version is before 5.2.1 (affects print-style function vulnerability)
  3. Check if ODBC extension is enabled
    Run `php -m` or check phpinfo() output for 'odbc' module
    Affected if ODBC extension is loaded and PHP version is before 5.2.1 (affects odbc_result_all vulnerability)
  4. Audit code for user input in format functions
    Search PHP source files for patterns like printf($var), print($var), sprintf($var) where $var could contain user-supplied data
    Affected if User-controlled input is passed directly to print-style functions without proper sanitization

A user is affected if running PHP version earlier than 5.2.1 on a 64-bit system with vulnerable code patterns, or using the odbc_result_all function with that PHP version.

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

Upgrade PHP to version 5.2.1 or later. If unable to upgrade immediately, audit code for direct use of user input in printf-style functions and sanitize all inputs before passing to these functions.

Fix this in PHP Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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