Comparison Overview
Sigmund Software

Sigmund Software
83 Wooster Heights Rd, Danbury, 06810, US
Last Update: 02/04/2026
Sigmund® is a leader in providing Software Solutions for Behavioral Health, Social Service and Addiction Treatment Providers nationwide. Sigmund’s suite of flexible features and cutting edge automation (including clinical documentation, EDI, benefits verification, epre...

IBM
International Business Machines Corp., Armonk, New York, 10504, US
Last Update: 24/09/2026
At IBM, we do more than work. We create. We create as technologists, developers, and engineers. We create with our partners. We create with our competitors. If you're searching for ways to make the world work better through technology and infrastructure, software and co...
Compliance Ranges Comparison

Sigmund Software







IBM






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Sigmund Software in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
IBM has 1174.51% more incidents than the average of all companies with at least one recorded incident.
Incident History - Sigmund Software (X = Date, Y = Severity)
Sigmund Software cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IBM (X = Date, Y = Severity)
IBM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sigmund Software

IBM
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)