Hulihanapplications maintains a small portfolio of web applications including DiamondList, Amethyst, and Hulihan BXR, where vulnerability disclosures cluster consistently around application-layer input and state-handling weaknesses such as cross-site request forgery, cross-site scripting, and SQL injection. These weakness classes reflect common validation and encoding challenges in web application development and merit attention from defenders managing these products in their environments. Current CVE counts, severity breakdowns, and exploitation status are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Hulihanapplications over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2010-4963HIGH SQL injection vulnerability in folder/list in Hulihan BXR 0.6.8 allows remote attackers to execute arbitrary SQL commands via the order_by parameter. | Oct 9, 2011 | 7.5 | 31 | NO | YES |
CVE-2010-3024MEDIUM Multiple cross-site request forgery (CSRF) vulnerabilities in user/main/update_user in DiamondList 0.1.6, and possibly earlier, allow remote attackers to hijack the authentication | Aug 16, 2010 | 6.8 | 29 | NO | YES |
CVE-2010-5085MEDIUM Multiple cross-site request forgery (CSRF) vulnerabilities in admin/update_user in Hulihan Amethyst 0.1.5, and possibly earlier, allow remote attackers to hijack the authentication | Feb 14, 2012 | 6.8 | 21 | NO | NO |
CVE-2010-3023MEDIUM Multiple cross-site scripting (XSS) vulnerabilities in DiamondList 0.1.6, and possibly earlier, allow remote attackers to inject arbitrary web script or HTML via the (1) category[d | Aug 16, 2010 | 4.3 | 21 | NO | YES |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Hulihanapplications.
Media articles that mention a CVE ID that affects a product developed by Hulihanapplications — matched by CVE ID, not by vendor name.