EL
Vendor
Elvinbts
9
CVEs
0
On KEV
0
New 30D
Products
Recent CVEs
| CVE | Product | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2009-2920 | EL Elvinbts Elvinbts | – | Aug 21 | Multiple cross-site scripting (XSS) vulnerabilities in Elvin 1.2.2 allow remote attackers to inject arbitrary web script or HTML via the (1) component and (2) priority parameters… |
| CVE-2009-2130 | EL Elvinbts Elvinbts | – | Jun 19 | Elvin 1.2.0 allows remote attackers to read the PHP source code of (1) login.ei, (2) jump_bug.ei, or (3) create_account.ei in inc/ via a direct request |
| CVE-2009-2129 | EL Elvinbts Elvinbts | – | Jun 19 | Cross-site request forgery (CSRF) vulnerability in login.php in Elvin 1.2.0 allows remote attackers to hijack the authentication of arbitrary users via a logout action |
| CVE-2009-2128 | EL Elvinbts Elvinbts | – | Jun 19 | SQL injection vulnerability in close_bug.php in Elvin before 1.2.1 allows remote attackers to execute arbitrary SQL commands via the title (aka subject) field |
| CVE-2009-2127 | EL Elvinbts Elvinbts | – | Jun 19 | Cross-site scripting (XSS) vulnerability in show_activity.php in Elvin 1.2.0 allows remote attackers to inject arbitrary web script or HTML via the id parameter |
| CVE-2009-2126 | EL Elvinbts Elvinbts | – | Jun 19 | Cross-site scripting (XSS) vulnerability in close_bug.php in Elvin before 1.2.1 allows remote attackers to inject arbitrary web script or HTML via the title (aka subject) field |
| CVE-2009-2125 | EL Elvinbts Elvinbts | – | Jun 19 | delete_bug.php in Elvin before 1.2.1 does not require administrative privileges, which allows remote authenticated users to bypass intended access restrictions and delete… |
| CVE-2009-2124 | EL Elvinbts Elvinbts | – | Jun 19 | Directory traversal vulnerability in page.php in Elvin 1.2.0 allows remote attackers to include and execute arbitrary local files via a |
| CVE-2009-2123 | EL Elvinbts Elvinbts | – | Jun 19 | Multiple SQL injection vulnerabilities in Elvin 1.2.0 allow remote attackers to execute arbitrary SQL commands via the (1) inUser (aka Username) and (2) inPass (aka Password)… |