Spiceworks

spiceworks

9 CVEs • 3 products

Products (3)

Click to collapse

Toggle

Help Desk Server

help_desk_server

CVEs (9)

CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS
CVE-2021-43609 1Spiceworks 1Help Desk Server Jun 17, 2026 Nov 9, 2023 N/A· v4 8.8 HIGH· v3 N/A· v2 An issue was discovered in Spiceworks Help Desk Server before 1.3.3. A Blind Boolean SQL injection vulnerability within the order_by_for_ticket function in app/models/reporting/database_query.rb allows an authenticated a...Show more An issue was discovered in Spiceworks Help Desk Server before 1.3.3. A Blind Boolean SQL injection vulnerability within the order_by_for_ticket function in app/models/reporting/database_query.rb allows an authenticated attacker to execute arbitrary SQL commands via the sort parameter. This can be leveraged to leak local files from the host system, leading to remote code execution (RCE) through deserialization of malicious data.Show less
CVE-2020-25901 1Spiceworks 1Spiceworks Jun 17, 2026 Dec 18, 2020 N/A· v4 6.1 MEDIUM· v3 5.8 MEDIUM· v2 Host Header Injection in Spiceworks 7.5.7.0 allowing the attacker to render arbitrary links that point to a malicious website with poisoned Host header webpages.
CVE-2020-23451 1Spiceworks 1Spiceworks Jun 17, 2026 Sep 15, 2020 N/A· v4 8.8 HIGH· v3 6.8 MEDIUM· v2 Spiceworks Version <= 7.5.00107 is affected by CSRF which can lead to privilege escalation via "/settings/v1/users" function.
CVE-2020-23450 1Spiceworks 1Spiceworks Jun 17, 2026 Sep 1, 2020 N/A· v4 5.4 MEDIUM· v3 3.5 LOW· v2 Spiceworks Version <= 7.5.00107 is affected by XSS. Any name typed on Custom Groups function is vulnerable to stored XSS as they displayed on http://127.0.0.1/inventory/groups/ without output sanitization.
CVE-2015-6021 1Spiceworks 1Desktop May 13, 2026 Apr 10, 2017 N/A· v4 6.1 MEDIUM· v3 4.3 MEDIUM· v2 Spiceworks Desktop before 2015-12-01 has XSS via an SNMP response.
CVE-2017-7237 1Spiceworks 1Spiceworks May 13, 2026 Apr 6, 2017 N/A· v4 9.8 CRITICAL· v3 7.5 HIGH· v2 The Spiceworks TFTP Server, as distributed with Spiceworks Inventory 7.5, allows remote attackers to access the Spiceworks data\configurations directory by leveraging the unauthenticated nature of the TFTP service for al...Show more The Spiceworks TFTP Server, as distributed with Spiceworks Inventory 7.5, allows remote attackers to access the Spiceworks data\configurations directory by leveraging the unauthenticated nature of the TFTP service for all clients who can reach UDP port 69, as demonstrated by a WRQ (aka Write request) operation for a configuration file or an executable file.Show less
CVE-2012-6658 1Spiceworks 1Spiceworks May 6, 2026 Sep 17, 2014 N/A· v4 N/A· v3 4.3 MEDIUM· v2 Multiple cross-site scripting (XSS) vulnerabilities in SpiceWorks 5.3.75941 allow remote attackers to inject arbitrary web script or HTML via the (1) syslocation, (2) syscontact, or (3) sysName configuration in snmpd.con...Show more Multiple cross-site scripting (XSS) vulnerabilities in SpiceWorks 5.3.75941 allow remote attackers to inject arbitrary web script or HTML via the (1) syslocation, (2) syscontact, or (3) sysName configuration in snmpd.conf. NOTE: this entry was SPLIT from CVE-2012-2956 per ADT2 due to different vulnerability types.Show less
CVE-2012-2956 1Spiceworks 1Spiceworks May 6, 2026 Sep 17, 2014 N/A· v4 N/A· v3 6.5 MEDIUM· v2 SQL injection vulnerability in SpiceWorks 5.3.75941 allows remote authenticated users to execute arbitrary SQL commands via the id parameter to api_v2.json. NOTE: this entry was SPLIT per ADT2 due to different vulnerabi...Show more SQL injection vulnerability in SpiceWorks 5.3.75941 allows remote authenticated users to execute arbitrary SQL commands via the id parameter to api_v2.json. NOTE: this entry was SPLIT per ADT2 due to different vulnerability types. CVE-2012-6658 is for the XSS.Show less
CVE-2014-3740 1Spiceworks 1Spiceworks May 6, 2026 Sep 11, 2014 N/A· v4 N/A· v3 3.5 LOW· v2 Cross-site scripting (XSS) vulnerability in SpiceWorks before 7.2.00195 allows remote authenticated users to inject arbitrary web script or HTML via the Summary field in a ticket request to the portal page.