Menu

Star on GitHub · 3.2k

CVE-2005-1898

5.0 · MEDIUM

The passthrough functionality in phpThumb.php in phpThumb() before 1.5.4 allows remote attackers to read files that are not images.

Published Jun 9, 2005phpthumbEPSS 1.37%

Overview

CVE-2005-1898 is a medium-severity vulnerability affecting phpthumb phpthumb. It was published on June 9, 2005 and has a CVSS 2.0 base score of 5.0 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 5.0, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

The passthrough functionality in phpThumb.php in phpThumb() before 1.5.4 allows remote attackers to read files that are not images.

Remediation

Check the references section for vendor advisories and patches from phpthumb. Update phpthumb to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2005-1898?

CVE-2005-1898 is a medium-severity vulnerability affecting phpthumb phpthumb. It was published on June 9, 2005 and has a CVSS 2.0 base score of 5.0 (MEDIUM).

How severe is CVE-2005-1898?

This vulnerability has a CVSS 2.0 base score of 5.0, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2005-1898?

Check the references section for vendor advisories and patches from phpthumb. Update phpthumb to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2005-1898?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-1898 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2005

View all