CVE-2008-6149: SQL Injection
First published: Mon Feb 16 2009(Updated: )
SQL injection vulnerability in the mDigg (com_mdigg) component 2.2.8 for Joomla! allows remote attackers to execute arbitrary SQL commands via the cagtegory parameter in a story_lists action to index.php.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| joomlaapps com mDigg | =2.2.8 | |
| Joomla |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2008-6149?
CVE-2008-6149 is classified as a high severity vulnerability due to its potential for arbitrary SQL command execution.
How do I fix CVE-2008-6149?
To fix CVE-2008-6149, update the mDigg component to a later version that addresses the SQL injection vulnerability.
What are the consequences of exploiting CVE-2008-6149?
Exploitation of CVE-2008-6149 can allow attackers to manipulate the database and gain unauthorized access to sensitive information.
Which component is affected by CVE-2008-6149?
The CVE-2008-6149 vulnerability affects the mDigg component version 2.2.8 for Joomla!.
Can CVE-2008-6149 be exploited remotely?
Yes, CVE-2008-6149 can be exploited remotely, allowing attackers to execute SQL commands via the vulnerable parameter.
- collector/nvd-historical
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/joomlaapps
- canonical/joomlaapps com mdigg
- version/joomlaapps com mdigg/2.2.8
- vendor/joomla
- canonical/joomla