CVE-2004-0067

The provided text describes a SQL injection vulnerability in PhpGedView 2.65beta5 and earlier, where the 'pids' parameter in timeline.php is not properly sanitized. It includes a sample URL demonstrating the injection point but lacks executable exploit code.

The provided text describes a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. The example URI demonstrates how an attacker could inject malicious HTML and script code.

The provided text describes a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. The example URI demonstrates how an attacker could inject hostile HTML and script code.

The provided text describes a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. An attacker could craft a malicious URI to execute arbitrary script code in the context of the victim's browser.

The provided text describes a SQL injection vulnerability in PhpGedView, detailing how unsanitized user input in the 'level' and 'parent' parameters can manipulate SQL queries. It includes example URLs demonstrating the exploit but lacks actual exploit code.

The provided text describes a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. The example URI demonstrates how an attacker could inject malicious HTML and script code.

This exploit demonstrates a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. The provided URLs show how an attacker can inject malicious HTML and script code via the 'day', 'month', and 'year' parameters.

The provided text describes a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. An attacker could craft a malicious URI to execute arbitrary script code in the context of the victim's browser session.

The provided text describes a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. It includes an example URI demonstrating the vulnerability but lacks executable exploit code.

The provided text describes a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. An attacker could craft a malicious URI to execute arbitrary script code in the context of the victim's browser.

This exploit demonstrates a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. An attacker can craft a malicious URI to execute arbitrary JavaScript in the context of the victim's browser session.

The provided text describes a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. An attacker could craft a malicious URI to execute arbitrary script code in the context of the victim's browser.

The exploit demonstrates a cross-site scripting (XSS) vulnerability in PhpGedView by injecting malicious HTML and script code via the 'path_to_find', 'pid1', and 'pid2' URI parameters. The vulnerability arises due to insufficient input sanitization, allowing arbitrary script execution in the context of the affected site.

The provided text describes a cross-site scripting (XSS) vulnerability in PhpGedView due to improper sanitization of user-supplied URI input. An attacker could craft a malicious URI to execute arbitrary script code in the context of the victim's browser.