yahoo
- Total products in the ecosystem
- 3
- Total vulnerabilities (90 days)
- 3
- Products & ServicesProducts & Services
- SolutionsSolutions
- PricingPricing
- CompanyCompany
- ResourcesResources
en
en
Verify to analyze this security profile
As of 09/18/2026, yahoo recorded 3 security vulnerabilities in the last 90 days across 2 products, including 1 rated High or above and 0 known exploited vulnerabilities (KEV) that should be prioritized for immediate remediation.
Over the last 90 days, CMAK had the most security vulnerabilities in the yahoo ecosystem, with 2 vulnerabilities—approximately 66.67% of the provider's total vulnerabilities during this period.
| Vulnerability | Exploitation status | Fix | Affected product | Published | Severity |
|---|---|---|---|---|---|
CVE-2026-92778CMAK through 3.0.0.6 Feature Gate Bypass via HTML Form Routes | Exploitation statusNot known exploited | FixYes | Affected productCMAK | Published09/16/2026 | SeverityMedium |
CVE-2026-92751CMAK through 3.0.0.6 Cross-Site Request Forgery via Missing CSRF Filter | Exploitation statusPublic exploit | FixYes | Affected productCMAK | Published09/16/2026 | SeverityHigh |
CVE-2026-57954Elide 7.1.17 - Permission Bypass in Sort Expression Validation | Exploitation statusPublic exploit | FixYes | Affected productelide | Published06/29/2026 | SeverityMedium |
CVE-2026-34043Serialize JavaScript has CPU Exhaustion Denial of Service via crafted array-like objects | Exploitation statusNot known exploited | FixYes | Affected productserialize-javascript | Published03/31/2026 | SeverityMedium |
CVE-2022-24827SQL Injection in elide-datastore-aggregation | Exploitation statusNot known exploited | FixNot confirmed | Affected productelide | Published04/11/2022 | SeverityHigh |
CVE-2020-5289Read permissions not enforced for client provided filter expressions in Elide http client | Exploitation statusNot confirmed | FixYes | Affected productelide | Published03/30/2020 | SeverityMedium |
CVE-2019-6035 | Exploitation statusNot confirmed | FixNot confirmed | Affected productAthenz | Published12/26/2019 | SeverityUnknown |
CVE-2019-16769Affected versions of serialize-javascript are vulnerable to Cross-site Scripting (XSS) | Exploitation statusNot confirmed | FixYes | Affected productserialize-javascript | Published12/05/2019 | SeverityMedium |
CVE-2017-2253 | Exploitation statusNot confirmed | FixNot confirmed | Affected productInstaller of Yahoo! Toolbar (for Internet explorer) | Published07/14/2017 | SeverityUnknown |
CVE-2014-7216 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published09/11/2015 | SeverityUnknown |
CVE-2014-5881 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published09/11/2014 | SeverityUnknown |
CVE-2013-6853 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/26/2014 | SeverityUnknown |
CVE-2013-6780 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/13/2013 | SeverityUnknown |
CVE-2013-4700 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published08/21/2013 | SeverityUnknown |
CVE-2013-4699 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published08/21/2013 | SeverityUnknown |
CVE-2013-4942 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/26/2013 | SeverityUnknown |
CVE-2013-4941 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/26/2013 | SeverityUnknown |
CVE-2013-4939 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/26/2013 | SeverityUnknown |
CVE-2013-4940 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/26/2013 | SeverityUnknown |
CVE-2013-4873 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/18/2013 | SeverityUnknown |
CVE-2013-2316 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published06/03/2013 | SeverityUnknown |
CVE-2013-2307 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published04/26/2013 | SeverityUnknown |
CVE-2012-5882 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/16/2012 | SeverityUnknown |
CVE-2012-5881 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/16/2012 | SeverityUnknown |
CVE-2012-5883 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/16/2012 | SeverityUnknown |
CVE-2012-2647 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/31/2012 | SeverityUnknown |
CVE-2012-2645 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/16/2012 | SeverityUnknown |
CVE-2012-0268 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/19/2012 | SeverityUnknown |
CVE-2010-4710 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/28/2011 | SeverityUnknown |
CVE-2010-4209 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2010 | SeverityUnknown |
CVE-2010-4207 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2010 | SeverityUnknown |
CVE-2010-4208 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published11/07/2010 | SeverityUnknown |
CVE-2009-4171 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/02/2009 | SeverityUnknown |
CVE-2008-2111 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/07/2008 | SeverityUnknown |
CVE-2008-0625 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published02/06/2008 | SeverityUnknown |
CVE-2008-0623 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published02/06/2008 | SeverityUnknown |
CVE-2008-0624 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published02/06/2008 | SeverityUnknown |
CVE-2007-6535 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/27/2007 | SeverityUnknown |
CVE-2007-6228 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/04/2007 | SeverityUnknown |
CVE-2002-2361 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published10/29/2007 | SeverityUnknown |
CVE-2007-5017 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published09/20/2007 | SeverityUnknown |
CVE-2007-4635 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published08/31/2007 | SeverityUnknown |
CVE-2007-4515 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published08/31/2007 | SeverityUnknown |
CVE-2007-4391 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published08/17/2007 | SeverityUnknown |
CVE-2007-4034 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/27/2007 | SeverityUnknown |
CVE-2007-3928 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/21/2007 | SeverityUnknown |
CVE-2007-3638 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published07/10/2007 | SeverityUnknown |
CVE-2007-3148 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published06/11/2007 | SeverityUnknown |
CVE-2007-3147 | Exploitation statusPublic exploit | FixNot confirmed | Affected productNot confirmed | Published06/11/2007 | SeverityUnknown |
CVE-2007-2385 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published04/30/2007 | SeverityUnknown |
CVE-2007-1680 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published04/06/2007 | SeverityUnknown |
CVE-2007-0868 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/09/2007 | SeverityUnknown |
CVE-2007-0768 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/06/2007 | SeverityUnknown |
CVE-2006-6603 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published12/15/2006 | SeverityUnknown |
CVE-2006-5563 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published10/27/2006 | SeverityUnknown |
CVE-2006-4975 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published09/25/2006 | SeverityUnknown |
CVE-2006-3298 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published06/29/2006 | SeverityUnknown |
CVE-2002-1665 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/28/2005 | SeverityUnknown |
CVE-2002-1664 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/28/2005 | SeverityUnknown |
CVE-2005-1671 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/19/2005 | SeverityUnknown |
CVE-2005-1618 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/16/2005 | SeverityUnknown |
CVE-2003-1135 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/10/2005 | SeverityUnknown |
CVE-2005-0737 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published03/13/2005 | SeverityUnknown |
CVE-2003-1129 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published03/12/2005 | SeverityUnknown |
CVE-2005-0242 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/18/2005 | SeverityUnknown |
CVE-2005-0243 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/18/2005 | SeverityUnknown |
CVE-2004-0043 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published01/14/2004 | SeverityUnknown |
CVE-2002-0032 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published04/02/2003 | SeverityUnknown |
CVE-2002-0031 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published06/11/2002 | SeverityUnknown |
CVE-2002-0322 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/03/2002 | SeverityUnknown |
CVE-2002-0320 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/03/2002 | SeverityUnknown |
CVE-2002-0321 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published05/03/2002 | SeverityUnknown |
CVE-2000-0047 | Exploitation statusNot confirmed | FixNot confirmed | Affected productNot confirmed | Published02/04/2000 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
.svg){kind=icon}
