Eggblog is a blogging platform with a modestly represented vulnerability profile centered on web application input-handling and access-control issues, including SQL injection, cross-site scripting, improper input validation, information disclosure, and link-resolution flaws. These vulnerabilities reflect common challenges in server-side web applications where user-supplied data intersects with database queries, page rendering, and file operations. Current severity, exploitation activity, and CVE counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Eggblog over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2008-0159MEDIUM SQL injection vulnerability in index.php in eggBlog 3.1.0 and earlier allows remote attackers to execute arbitrary SQL commands via the eggblogpassword parameter in a cookie. | Jan 9, 2008 | 6.8 | 27 | NO | YES |
CVE-2008-1626HIGH SQL injection vulnerability in eggBlog before 4.0.1 allows remote attackers to execute arbitrary SQL commands via an unspecified cookie. NOTE: this might overlap CVE-2008-0159. | Apr 2, 2008 | 7.5 | 22 | NO | NO |
CVE-2011-3732MEDIUM eggBlog 4.1.2 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated | Sep 23, 2011 | 5.0 | 18 | NO | NO |
CVE-2007-2978MEDIUM Session fixation vulnerability in eggblog 3.1.0 and earlier allows remote attackers to hijack web sessions by setting the PHPSESSID parameter. | Jun 1, 2007 | 6.8 | 18 | NO | NO |
CVE-2007-5980MEDIUM Cross-site scripting (XSS) vulnerability in home/rss.php in eggblog before 3.1.1 allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO (PHP_SELF). | Nov 15, 2007 | 4.3 | 14 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Eggblog.
Media articles that mention a CVE ID that affects a product developed by Eggblog — matched by CVE ID, not by vendor name.