RunCMS Myarticles Module 0.6 topics.php topic_id sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in RunCMS Myarticles Module 0.6. This impacts an unknown function of the file topics.php. Performing a manipulation of the argument topic_id results in sql injection. This vulnerability is cataloged as CVE-2008-2084. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Details
A vulnerability, which was classified as critical, was found in RunCMS Myarticles Module 0.6 (Content Management System). This affects an unknown code of the file topics.php. The manipulation of the argument topic_id 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 summary by CVE is:
SQL injection vulnerability in topics.php in the MyArticles 0.6 beta-1 module for RunCMS allows remote attackers to execute arbitrary SQL commands via the topic_id parameter in a listarticles action.
The weakness was shared 05/05/2008 (Website). The advisory is shared at milw0rm.com. This vulnerability is uniquely identified as CVE-2008-2084 since 05/05/2008. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The exploit is shared for download at exploit-db.com. It is declared as highly functional. By approaching the search of inurl:topics.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 X-Force (42016), Exploit-DB (5505) and SecurityFocus (BID 28952†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.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
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
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/26/2008 🔍05/05/2008 🔍
05/05/2008 🔍
05/05/2008 🔍
03/16/2015 🔍
10/21/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Not defined
CVE: CVE-2008-2084 (🔍)
GCVE (CVE): GCVE-0-2008-2084
GCVE (VulDB): GCVE-100-42249
X-Force: 42016 - MyArticles module for RunCMS topics.php SQL injection
SecurityFocus: 28952
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/16/2015 17:00Updated: 10/21/2024 07:28
Changes: 03/16/2015 17:00 (52), 11/12/2017 21:03 (4), 07/31/2021 21:07 (4), 10/21/2024 07:28 (15)
Complete: 🔍
Cache ID: 216:ED8:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.