Comparison Overview
Department for Culture, Media and Sport
Department for Culture, Media and Sport
Parliament Street, London, SW1A 2BQ, GB
Last Update: 04/04/2026
The Department for Culture, Media and Sport will focus on supporting culture, arts, media, sport, tourism and civil society across every part of England — recognising the UK’s world-leading position in these areas and the importance of these sectors in contributing so m...
City of Cape Town
12 Hertzog Blvd, Cape Town, Western Cape, ZA, 8001
Last Update: 02/04/2026
Cape Town, or the Mother City, is South Africa’s oldest city, its second-most populous and the legislative capital. It is made up of a diverse population, a rich history, world-famous tourist attractions and an exciting calendar of international and local events. More ...
Compliance Ranges Comparison
Department for Culture, Media and Sport
City of Cape Town
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Department for Culture, Media and Sport in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for City of Cape Town in 2026.
Incident History - Department for Culture, Media and Sport (X = Date, Y = Severity)
Department for Culture, Media and Sport cyber incidents detection timeline including parent company and subsidiaries.
Incident History - City of Cape Town (X = Date, Y = Severity)
City of Cape Town cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Department for Culture, Media and Sport
City of Cape Town
FAQ
Latest Global CVEs
PraisonAI before 1.5.115 contains a path traversal vulnerability in MultiAgentMonitor that fails to sanitize agent IDs when building file paths. Attackers can include traversal sequences like ../ in agent IDs to read, write, or overwrite arbitrary files, enabling sensitive disclosure, denial of service, or code execution.
PraisonAI before 1.5.115 contains an information disclosure vulnerability in the MultiAgentLedger component that allows attackers to access sensitive data by registering agents with duplicate IDs. Attackers can exploit the lack of agent ID uniqueness enforcement to share ledger instances and expose system prompts and conversation history between agents.
PraisonAI before 1.5.128 contains a cross-origin agent execution vulnerability in the AGUI endpoint that allows remote attackers to trigger arbitrary agent execution. The POST /agui endpoint lacks authentication and hardcodes Access-Control-Allow-Origin: * headers, combined with Starlette's Content-Type-agnostic JSON parsing, enabling attackers to bypass CORS preflight checks via simple requests and exfiltrate sensitive agent responses including tool execution results and environment data.
PraisonAI before 4.5.128 contains an arbitrary shell command execution vulnerability where the UI modules hardcode approval_mode to auto, overriding administrator configuration from PRAISON_APPROVAL_MODE environment variable. Authenticated attackers can instruct the LLM agent to execute arbitrary shell commands via subprocess.run with shell=True, bypassing the manual approval gate and insufficient command sanitization blocklists.
PraisonAI before 1.5.128 caches tool approval decisions by tool name only, not by invocation arguments, allowing subsequent execute_command calls to bypass approval prompts. Attackers can exploit this by obtaining initial approval for a benign command, then silently exfiltrate API keys and credentials via subsequent shell commands without user consent.