dbcve.org
PhpmybackupproApplication

CVE-2009-4050

MEDIUM · 5.0 CVSS v2.0 Published 2009-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Directory traversal vulnerability in get_file.php in phpMyBackupPro 2.1 allows remote attackers to read arbitrary files via directory traversal sequences in the view 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 confidence

Directory traversal vulnerability in phpMyBackupPro 2.1's get_file.php allows remote attackers to read arbitrary files by injecting directory traversal sequences (e.g., ../../) into the view parameter without proper sanitization, exposing sensitive server files to unauthenticated attackers.

MitigationImplement strict input validation on the view parameter to restrict it to expected values, use realpath() to resolve and validate the final path, and consider applying additional web server-level restrictions on accessible directories.

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
PhpmybackupproApplication
Affected:= 2.1

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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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. Identify phpMyBackupPro installation and version
    Locate the phpMyBackupPro installation directory in your web root (commonly /phpMyBackupPro, /phpmybackup, or similar). Check for a version file or index.php that displays the version number. Typical paths include /var/www/html/phpMyBackupPro, /home/user/public_html/phpMyBackupPro, or C:\inetpub\wwwroot\phpMyBackupPro depending on your setup.
    Affected if The installed version is phpMyBackupPro 2.1 exactly.
  2. Verify get_file.php exists
    Check if the file get_file.php is present within the phpMyBackupPro installation directory. This file is typically located at /path/to/phpMyBackupPro/get_file.php.
    Affected if get_file.php exists in the phpMyBackupPro 2.1 installation directory.
  3. Inspect get_file.php for vulnerable parameter handling
    Open get_file.php and examine the code around line 20-40 where the 'view' parameter is processed. Look for code that uses $_GET['view'] or $_REQUEST['view'] directly in file operations (such as file_get_contents, fopen, include, or readfile) without sanitization using functions like realpath(), basename(), or input validation.
    Affected if The 'view' parameter is used in file operations without proper path sanitization using realpath() or equivalent validation.
  4. Confirm web server access to vulnerable script
    Verify that get_file.php is web-accessible by attempting to access it via HTTP (e.g., http://yourserver/phpMyBackupPro/get_file.php) or by checking the web server configuration (Apache httpd.conf, Nginx config, or IIS web.config) to confirm the directory is not blocked from execution.
    Affected if get_file.php is accessible via HTTP and the web server executes PHP files in that directory.

You are affected if phpMyBackupPro version 2.1 is installed, get_file.php exists, and the 'view' parameter in get_file.php is processed without directory traversal protection.

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 on the view parameter to restrict it to expected values, use realpath() to resolve and validate the final path, and consider applying additional web server-level restrictions on accessible directories.

Fix this in Phpmybackuppro Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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