dbcve.org
PhpgedviewApplication

CVE-2004-0065

HIGH · 7.5 CVSS v2.0 Published 2004-02-17
Fix available
A fix is available. Upgrade to after 2.65 or later.
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 SQL injection vulnerabilities in phpGedView before 2.65 allow remote attackers to execute arbitrary SQL via (1) timeline.php and (2) placelist.php.

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

SQL injection vulnerabilities in phpGedView timeline.php and placelist.php allow remote attackers to inject arbitrary SQL commands via unsanitized user input, potentially leading to data exfiltration or database compromise.

MitigationUpgrade to phpGedView 2.65 or later which contains the patched code. As a temporary measure, implement input validation and web application firewall rules to block SQL injection payloads.

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
PhpgedviewApplication
Affected:<= 2.65

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 phpGedView installation
    Search the web root for phpGedView files, typically in a directory named 'phpgedview' or check for gedview.php, timeline.php, or placelist.php files
    Affected if phpGedView files are found on the system
  2. Identify installed phpGedView version
    Check the version.php file or any version file within the phpGedView directory, or view the page source of the main index page for version information
    Affected if The version is 2.65 or lower
  3. Locate vulnerable script files
    Check if timeline.php and placelist.php exist in the web-accessible phpGedView directory
    Affected if These PHP files are present and accessible via the web server
  4. Verify SQL injection point exists
    Examine the source code of timeline.php and placelist.php for direct use of $_GET, $_POST, or $_REQUEST variables in SQL queries without sanitization functions like mysql_real_escape_string or parameterized queries
    Affected if User-supplied parameters are used directly in SQL queries without being escaped or parameterized

The system is affected if phpGedView version 2.65 or lower is installed with the vulnerable timeline.php or placelist.php scripts accessible and using unsanitized user input in SQL queries.

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
Upgrade available Upgrade to a release after 2.65
Interim mitigation

Upgrade to phpGedView 2.65 or later which contains the patched code. As a temporary measure, implement input validation and web application firewall rules to block SQL injection payloads.

Fix this in Phpgedview Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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