| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Beehive Forum 0.1.1. This issue affects some unknown processing of the file index.php. This manipulation of the argument webtag causes sql injection. The identification of this vulnerability is CVE-2005-2421. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Beehive Forum 0.1.1 (Forum Software). It has been declared as critical. Affected by this vulnerability is some unknown functionality of the file index.php. The manipulation of the argument webtag with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Multiple SQL injection vulnerabilities in index.php and other pages in Beehive Forum allow remote attackers to execute arbitrary SQL commands via the webtag parameter.
The weakness was shared 08/03/2005 by thegreatone2176 (Website). The advisory is shared at marc.theaimsgroup.com. This vulnerability is known as CVE-2005-2421 since 08/03/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.
The vulnerability is also documented in the databases at X-Force (21535), SecurityFocus (BID 14361†) and Secunia (SA16217†). The entries VDB-25911 and VDB-25910 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/25/2005 🔍07/26/2005 🔍
08/03/2005 🔍
08/03/2005 🔍
08/03/2005 🔍
03/11/2015 🔍
07/29/2017 🔍
Sources
Advisory: marc.theaimsgroup.comResearcher: thegreatone2176
Status: Confirmed
CVE: CVE-2005-2421 (🔍)
GCVE (CVE): GCVE-0-2005-2421
GCVE (VulDB): GCVE-100-25909
X-Force: 21535 - Beehive forum webtag SQL injection
SecurityFocus: 14361 - Beehive Forum Webtag Multiple SQL Injection Vulnerabilities
Secunia: 16217 - Beehive Forum "webtag" SQL Injection Vulnerability, Moderately Critical
See also: 🔍
Entry
Created: 03/11/2015 23:39Updated: 07/29/2017 18:02
Changes: 03/11/2015 23:39 (59), 07/29/2017 18:02 (1)
Complete: 🔍
Cache ID: 216::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.