Comparison Overview
Ziff Davis Performance Marketing
Ziff Davis Performance Marketing
3700 N Capital of Texas Hwy #100,, Austin, undefined, TX 78746, US
Last Update: 06/03/2026
ZDPM is the coming together of Salesify and DemandShore. Collectively, we’ve been in the B2B Tech Performance Marketing business since 2004. Our years of experience, both in terms of people as well as processes are unparalleled in the industry today. We are also a Grea...
SEO
Melbourne, 3121, AU
Last Update: 31/03/2026
It’s been over 15 years since SEO.com.au started, and we’re proud to say we lead the way because we’ve got the experience and the talent to get you great results. What makes us work? Quite honestly, it’s the relationships we build with our clients that let us achieve wh...
Compliance Ranges Comparison
Ziff Davis Performance Marketing
SEO
Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Ziff Davis Performance Marketing in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for SEO in 2026.
Incident History - Ziff Davis Performance Marketing (X = Date, Y = Severity)
Ziff Davis Performance Marketing cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SEO (X = Date, Y = Severity)
SEO cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ziff Davis Performance Marketing
SEO
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.