Phorum 3.4/3.4.1/3.4.2 Error Message Path information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Phorum 3.4/3.4.1/3.4.2. It has been classified as problematic. This affects an unknown part of the component Error Message Handler. This manipulation causes information disclosure (Path). This vulnerability is tracked as CVE-2003-1486. No exploit exists.
Details
A vulnerability has been found in Phorum 3.4/3.4.1/3.4.2 (Forum Software) and classified as problematic. Affected by this vulnerability is an unknown code block of the component Error Message Handler. The manipulation with an unknown input leads to a information disclosure vulnerability (Path). The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect integrity. The summary by CVE is:
Phorum 3.4 through 3.4.2 allows remote attackers to obtain the full path of the web server via an incorrect HTTP request to (1) smileys.php, (2) quick_listrss.php, (3) purge.php, (4) news.php, (5) memberlist.php, (6) forum_listrss.php, (7) forum_list_rdf.php, (8) forum_list.php, or (9) move.php, which leaks the information in an error message.
The weakness was disclosed 12/31/2003 with ProCheckUp (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2003-1486 since 10/24/2007. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 11217 (Phorum Multiple Path Disclosure Vulnerabilities).
The vulnerability is also documented in the databases at X-Force (12499) and SecurityFocus (BID 7571†). The entries VDB-21382, VDB-21383, VDB-21384 and VDB-21398 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: PathClass: Information disclosure / Path
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/13/2003 🔍12/31/2003 🔍
12/31/2003 🔍
10/24/2007 🔍
09/01/2014 🔍
07/13/2025 🔍
Sources
Advisory: securityfocus.com⛔Organization: ProCheckUp
Status: Confirmed
CVE: CVE-2003-1486 (🔍)
GCVE (CVE): GCVE-0-2003-1486
GCVE (VulDB): GCVE-100-21397
X-Force: 12499 - Phorum multiple script path disclosure
SecurityFocus: 7571 - Phorum Multiple Path Disclosure Vulnerabilities
See also: 🔍
Entry
Created: 09/01/2014 16:44Updated: 07/13/2025 22:48
Changes: 09/01/2014 16:44 (50), 06/17/2018 09:37 (6), 07/13/2025 22:48 (18)
Complete: 🔍
Cache ID: 216:687:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.