Comparison Overview
State Budget Office of Michigan
State Budget Office of Michigan
111 S Capitol Ave, Lansing, 48922, US
Last Update: 17/12/2025
The Michigan State Budget Office (SBO) is responsible for coordinating all aspects of the state budget, including development of the Executive Budget recommendation, presentation of the budget to the Legislature, negotiation of the enacted budget with the Legislature, i...
Malmö stad
August Palms plats 1, Malmö, 205 80, SE
Last Update: 03/04/2026
Bli en samhällsbyggare – jobba i Malmö stad! Genom att arbeta i Malmö stad får du möjlighet att arbeta med hållbar samhällsutveckling. Som en samhällsbyggare spelar du en viktig roll i Malmös utveckling och därför ser vi oss som framtidens arbetsplats. Människors lik...
Compliance Ranges Comparison
State Budget Office of Michigan
Malmö stad
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for State Budget Office of Michigan in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Malmö stad in 2026.
Incident History - State Budget Office of Michigan (X = Date, Y = Severity)
State Budget Office of Michigan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Malmö stad (X = Date, Y = Severity)
Malmö stad cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
State Budget Office of Michigan
Malmö stad
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)