Menu

Star on GitHub · 3.2k

CVE-2005-0659

5.0 · MEDIUM

phpBB 2.0.13 and earlier allows remote attackers to obtain sensitive information via a direct request to oracle.php, which reveals the path in a PHP error message.

Published May 2, 2005phpbb_groupEPSS 1.55%

Overview

CVE-2005-0659 is a medium-severity vulnerability affecting phpbb_group phpbb. It was published on May 2, 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

phpBB 2.0.13 and earlier allows remote attackers to obtain sensitive information via a direct request to oracle.php, which reveals the path in a PHP error message.

Remediation

Check the references section for vendor advisories and patches from phpbb_group. Update phpbb 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-0659?

CVE-2005-0659 is a medium-severity vulnerability affecting phpbb_group phpbb. It was published on May 2, 2005 and has a CVSS 2.0 base score of 5.0 (MEDIUM).

How severe is CVE-2005-0659?

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-0659?

Check the references section for vendor advisories and patches from phpbb_group. Update phpbb 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-0659?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-0659 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