CVE-2008-0446: SQL Injection
First published: Thu Jan 24 2008(Updated: )
SQL injection vulnerability in voircom.php in LulieBlog 1.02 allows remote attackers to execute arbitrary SQL commands via the id parameter.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Lulieblog | =1.02 |
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-0446?
CVE-2008-0446 is considered to have a high severity due to the potential for remote SQL injection attacks.
How do I fix CVE-2008-0446?
To fix CVE-2008-0446, validate and sanitize all user inputs, especially the 'id' parameter in voircom.php.
Which software versions are affected by CVE-2008-0446?
CVE-2008-0446 affects LulieBlog version 1.02.
What kind of attacks can be executed due to CVE-2008-0446?
CVE-2008-0446 allows remote attackers to execute arbitrary SQL commands, potentially compromising the database.
Is CVE-2008-0446 still a concern for users of LulieBlog?
Yes, CVE-2008-0446 remains a concern for users of LulieBlog 1.02 if they have not implemented necessary security measures.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/references
- agent/last-modified-date
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/julian pawlowski
- canonical/lulieblog
- version/lulieblog/1.02