| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Phorum. Affected by this issue is some unknown functionality of the file admin.php. The manipulation results in sql injection. This vulnerability is reported as CVE-2007-2249. The attack can be launched remotely. Moreover, an exploit is present.
Details
A vulnerability classified as critical has been found in Phorum (Forum Software) (unknown version). Affected is an unknown code block of the file admin.php. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was disclosed 04/19/2007 by Janek Vind (Website). The advisory is available at waraxe.us. This vulnerability is traded as CVE-2007-2249. It is possible to launch the attack remotely. Technical details and a public exploit are known. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept. By approaching the search of inurl:admin.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Exploit-DB (29889), SecurityFocus (BID 23616†), OSVDB (35063†), Secunia (SA24932†) and SecurityTracker (ID 1017936†). The entries VDB-36470, VDB-36469, VDB-36387 and VDB-36386 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/19/2007 🔍04/20/2007 🔍
04/20/2007 🔍
04/23/2007 🔍
04/25/2007 🔍
05/08/2016 🔍
11/07/2025 🔍
Sources
Advisory: waraxe.usResearcher: Janek Vind
Status: Not defined
CVE: CVE-2007-2249 (🔍)
GCVE (CVE): GCVE-0-2007-2249
GCVE (VulDB): GCVE-100-85482
SecurityFocus: 23616 - Phorum Multiple Input Validation Vulnerabilities
Secunia: 24932 - Phorum Multiple Vulnerabilities, Less Critical
OSVDB: 35063 - Phorum admin.php badwords/banlist Module SQL Injection
SecurityTracker: 1017936
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/08/2016 21:52Updated: 11/07/2025 04:47
Changes: 05/08/2016 21:52 (50), 12/07/2018 12:22 (2), 08/10/2022 10:11 (3), 08/10/2022 10:18 (7), 02/02/2025 22:18 (19), 11/07/2025 04:47 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.