- Products & ServicesProducts & Services
- SolutionsSolutions
- PricingPricing
- CompanyCompany
- ResourcesResources
en
en
Severity across 3 analyzed records
As of 09/28/2026, within CyStack's analyzed data, owncloud_server has 0 security vulnerabilities published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of owncloud_server and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2023-49105 | Exploitation statusKEV | FixNot confirmed | Published11/21/2023 | SeverityCritical |
CVE-2021-29659 | Exploitation statusNot confirmed | FixNot confirmed | Published05/20/2021 | SeverityUnknown |
CVE-2020-36252 | Exploitation statusNot confirmed | FixNot confirmed | Published02/19/2021 | SeverityMedium |
CVE-2015-4715 | Exploitation statusNot confirmed | FixNot confirmed | Published02/17/2020 | SeverityUnknown |
CVE-2014-2052 | Exploitation statusNot confirmed | FixNot confirmed | Published02/11/2020 | SeverityUnknown |
CVE-2014-2050 | Exploitation statusNot confirmed | FixNot confirmed | Published01/23/2020 | SeverityUnknown |
CVE-2013-0203 | Exploitation statusNot confirmed | FixNot confirmed | Published11/22/2019 | SeverityUnknown |
CVE-2013-0202 | Exploitation statusNot confirmed | FixNot confirmed | Published11/22/2019 | SeverityUnknown |
CVE-2016-1501 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2016 | SeverityUnknown |
CVE-2016-1499 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2016 | SeverityUnknown |
CVE-2016-1500 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2016 | SeverityUnknown |
CVE-2016-1498 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2016 | SeverityUnknown |
CVE-2015-7699 | Exploitation statusNot confirmed | FixNot confirmed | Published10/26/2015 | SeverityUnknown |
CVE-2015-6500 | Exploitation statusNot confirmed | FixNot confirmed | Published10/26/2015 | SeverityUnknown |
CVE-2015-6670 | Exploitation statusNot confirmed | FixNot confirmed | Published10/26/2015 | SeverityUnknown |
CVE-2015-4718 | Exploitation statusNot confirmed | FixNot confirmed | Published10/21/2015 | SeverityUnknown |
CVE-2015-4716 | Exploitation statusNot confirmed | FixNot confirmed | Published10/21/2015 | SeverityUnknown |
CVE-2015-4717 | Exploitation statusNot confirmed | FixNot confirmed | Published10/21/2015 | SeverityUnknown |
CVE-2015-5954 | Exploitation statusNot confirmed | FixNot confirmed | Published10/21/2015 | SeverityUnknown |
CVE-2015-5953 | Exploitation statusNot confirmed | FixNot confirmed | Published10/21/2015 | SeverityUnknown |
CVE-2015-3013 | Exploitation statusNot confirmed | FixNot confirmed | Published05/08/2015 | SeverityUnknown |
CVE-2014-9042 | Exploitation statusNot confirmed | FixNot confirmed | Published02/04/2015 | SeverityUnknown |
CVE-2014-9043 | Exploitation statusNot confirmed | FixNot confirmed | Published02/04/2015 | SeverityUnknown |
CVE-2014-9046 | Exploitation statusNot confirmed | FixNot confirmed | Published02/04/2015 | SeverityUnknown |
CVE-2014-9047 | Exploitation statusNot confirmed | FixNot confirmed | Published02/04/2015 | SeverityUnknown |
CVE-2014-9041 | Exploitation statusNot confirmed | FixNot confirmed | Published02/04/2015 | SeverityUnknown |
CVE-2014-9044 | Exploitation statusNot confirmed | FixNot confirmed | Published02/04/2015 | SeverityUnknown |
CVE-2014-9045 | Exploitation statusNot confirmed | FixNot confirmed | Published02/04/2015 | SeverityUnknown |
CVE-2014-9048 | Exploitation statusNot confirmed | FixNot confirmed | Published02/04/2015 | SeverityUnknown |
CVE-2014-9049 | Exploitation statusNot confirmed | FixNot confirmed | Published02/04/2015 | SeverityUnknown |
CVE-2014-2044 | Exploitation statusPublic exploit | FixNot confirmed | Published10/06/2014 | SeverityUnknown |
CVE-2014-4929 | Exploitation statusNot confirmed | FixNot confirmed | Published08/20/2014 | SeverityUnknown |
CVE-2013-0302 | Exploitation statusNot confirmed | FixNot confirmed | Published06/05/2014 | SeverityUnknown |
CVE-2013-0304 | Exploitation statusNot confirmed | FixNot confirmed | Published06/05/2014 | SeverityUnknown |
CVE-2014-2051 | Exploitation statusNot confirmed | FixNot confirmed | Published06/05/2014 | SeverityUnknown |
CVE-2014-2055 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2012-5056 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-2056 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-3835 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-3834 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-2054 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2012-5336 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-3832 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2012-5057 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2013-0204 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-3833 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-3836 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-3837 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2013-1941 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-2053 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-3838 | Exploitation statusNot confirmed | FixNot confirmed | Published06/04/2014 | SeverityUnknown |
CVE-2014-2585 | Exploitation statusNot confirmed | FixNot confirmed | Published03/23/2014 | SeverityUnknown |
CVE-2013-0303 | Exploitation statusNot confirmed | FixNot confirmed | Published03/23/2014 | SeverityUnknown |
CVE-2014-2057 | Exploitation statusNot confirmed | FixNot confirmed | Published03/23/2014 | SeverityUnknown |
CVE-2013-7344 | Exploitation statusNot confirmed | FixNot confirmed | Published03/23/2014 | SeverityUnknown |
CVE-2013-0201 | Exploitation statusNot confirmed | FixNot confirmed | Published03/18/2014 | SeverityUnknown |
CVE-2013-0300 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-0299 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-0301 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-1822 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2150 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2048 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2041 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2014-2049 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2040 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-1963 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-1851 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-1939 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2089 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2039 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2044 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2043 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2047 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2042 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-1850 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2014-2047 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2086 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2149 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-0298 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-0297 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-0307 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2014 | SeverityUnknown |
CVE-2013-2045 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2014 | SeverityUnknown |
CVE-2013-2046 | Exploitation statusNot confirmed | FixNot confirmed | Published03/07/2014 | SeverityUnknown |
CVE-2013-1967 | Exploitation statusNot confirmed | FixNot confirmed | Published02/05/2014 | SeverityUnknown |
CVE-2013-6403 | Exploitation statusNot confirmed | FixNot confirmed | Published12/24/2013 | SeverityUnknown |
CVE-2013-1942 | Exploitation statusNot confirmed | FixNot confirmed | Published08/15/2013 | SeverityUnknown |
CVE-2012-5665 | Exploitation statusNot confirmed | FixNot confirmed | Published01/03/2013 | SeverityUnknown |
CVE-2012-5666 | Exploitation statusNot confirmed | FixNot confirmed | Published01/03/2013 | SeverityUnknown |
CVE-2012-5606 | Exploitation statusNot confirmed | FixNot confirmed | Published12/18/2012 | SeverityUnknown |
CVE-2012-5609 | Exploitation statusNot confirmed | FixNot confirmed | Published12/18/2012 | SeverityUnknown |
CVE-2012-5607 | Exploitation statusNot confirmed | FixNot confirmed | Published12/18/2012 | SeverityUnknown |
CVE-2012-5608 | Exploitation statusNot confirmed | FixNot confirmed | Published12/18/2012 | SeverityUnknown |
CVE-2012-4393 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2012 | SeverityUnknown |
CVE-2012-4389 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2012 | SeverityUnknown |
CVE-2012-4394 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2012 | SeverityUnknown |
CVE-2012-4396 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2012 | SeverityUnknown |
CVE-2012-4391 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2012 | SeverityUnknown |
CVE-2012-4397 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2012 | SeverityUnknown |
CVE-2012-4753 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2012 | SeverityUnknown |
CVE-2012-4390 | Exploitation statusNot confirmed | FixNot confirmed | Published09/05/2012 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan