Comparison Overview
Progress WhatsUp Gold
Progress WhatsUp Gold
15 Wayside Rd, Burlington, 01803, US
Last Update: 01/04/2026
WhatsUp Gold provides complete visibility into the status and performance of applications, network devices and servers in the cloud or on-premises. Discover Your Network: WhatsUp Gold’s powerful layer 2/3 discovery results in a detailed interactive map of your entire n...
Amazon
2127 7th Ave., Seattle, 98109, US
Last Update: 09/08/2026
Amazon is guided by four principles: customer obsession rather than competitor focus, passion for invention, commitment to operational excellence, and long-term thinking. We are driven by the excitement of building technologies, inventing products, and providing service...
Compliance Ranges Comparison
Progress WhatsUp Gold
Amazon
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Progress WhatsUp Gold in 2026.
Incidents vs Software Development Industry Avg (This Year)
Amazon has 967.96% more incidents than the average of all companies with at least one recorded incident.
Incident History - Progress WhatsUp Gold (X = Date, Y = Severity)
Progress WhatsUp Gold cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amazon (X = Date, Y = Severity)
Amazon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Progress WhatsUp Gold
Amazon
FAQ
Latest Global CVEs
A vulnerability was found in ggml-org llama.cpp bec4772f6. The impacted element is the function deserialize_tensor of the file ggml/src/ggml-rpc/ggml-rpc.cpp of the component ggml-RPC Server. Performing a manipulation of the argument op/op_params results in deserialization. The attack may be initiated remotely. This vulnerability is distinct from CVE-2026-34159 (GHSA-j8rj-fmpv-wcxw, PR #20908), which only added a buffer==nullptr rejection in create_node() and does not validate op or op_params. The reported GitHub issue was closed automatically due to inactivity.
A vulnerability has been found in CTFd up to 3.8.4. The affected element is the function _is_safe_url of the file CTFd/utils/validators/__init__.py. Such manipulation of the argument Next leads to open redirect. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 5d8515842fd1ab2c3a9f2dde9ffca907aa334ea9. Upgrading the affected component is recommended.
- https://github.com/CTFd/CTFd/
- https://github.com/CTFd/CTFd/commit/5d8515842fd1ab2c3a9f2dde9ffca907aa334ea9
- https://github.com/CTFd/CTFd/pull/3026
- https://github.com/CTFd/CTFd/releases/tag/3.8.4
- https://mblunt.dev/writeups/ctfd-open-redirect/
- https://vuldb.com/cve/CVE-2026-78145
- https://vuldb.com/submit/882469
- https://vuldb.com/vuln/394533
- https://vuldb.com/vuln/394533/cti
A vulnerability was identified in code-projects Barangay Resident Profiling Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /boarders.php of the component Boarder Management Module. Such manipulation of the argument ID leads to authorization bypass. The attack can be executed remotely. The exploit is publicly available and might be used.
A vulnerability was determined in code-projects Barangay Resident Profiling Management System 1.0. Affected is an unknown function of the file residents.php of the component Resident Search Functionality. This manipulation of the argument Search causes sql injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.
A vulnerability was found in code-projects Barangay Resident Profiling Management System 1.0. This impacts an unknown function of the file /archived_records.php of the component Restore/Delete. The manipulation of the argument resident_id results in authorization bypass. The attack may be launched remotely. The exploit has been made public and could be used.