CVE-2008-6134: SQL Injection
First published: Sat Feb 14 2009(Updated: )
SQL injection vulnerability in EveryBlog 5.x and 6.x, a module for Drupal, allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Drupal | =5.0 | |
| Drupal | =6.0 | |
| Drupal |
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-6134?
CVE-2008-6134 is classified as a medium severity SQL injection vulnerability.
How do I fix CVE-2008-6134?
To fix CVE-2008-6134, upgrade to EveryBlog versions 5.1 or 6.1 or later.
Which versions of EveryBlog are affected by CVE-2008-6134?
CVE-2008-6134 affects EveryBlog versions 5.x and 6.x.
Can CVE-2008-6134 be exploited remotely?
Yes, CVE-2008-6134 allows remote attackers to execute arbitrary SQL commands.
What software contains the CVE-2008-6134 vulnerability?
CVE-2008-6134 is found in the EveryBlog module for Drupal.
- 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/drupal
- canonical/drupal
- version/drupal/5.0
- version/drupal/6.0