Comparison Overview

Media Trust Limited

VS

Conexus Financial

Media Trust Limited

None
Last Update: 2025-11-21
View Profile
Between 800 and 849
http://www.dailytrust.com

Media Trust Limited is a publishing company with corporate headquarters based in Abuja, Nigeria. Currently, there are four publications in the Trust stable: Daily Trust, Weekly Trust, which is a Saturday newspaper, Sunday Trust, and a Hausa language weekly, Aminiya. These are printed simultaneously in Abuja, Kano, and (in preparation), Maiduguri. The company has plans to add television and radio channels in its operations.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 239
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Conexus Financial

L9 17-19 Bridge Street, Sydney, 2000, AU
Last Update: 2025-11-26
Between 750 and 799
http://www.conexusfinancial.com.au

Conexus Financial is an independent publisher and conference producer specialising in financial services. Headquartered in Australia, it connects senior executives and leaders in institutional investment, superannuation and wealth management around the world. Through its media and events, it advocates for change in the industry, impacting some $50 trillion in fiduciary and advised capital. A purpose-led company, it seeks to influence the global financial system in a way that empowers and creates better outcomes for consumers.

NAICS: 511
NAICS Definition: Publishing Industries (except Internet)
Employees: 29
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Media Trust Limited
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/conexus-financial.jpeg
Conexus Financial
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Media Trust Limited
100%
Compliance Rate
0/4 Standards Verified
Conexus Financial
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Media Trust Limited in 2025.

Incidents vs Book and Periodical Publishing Industry Average (This Year)

No incidents recorded for Conexus Financial in 2025.

Incident History — Media Trust Limited (X = Date, Y = Severity)

Media Trust Limited cyber incidents detection timeline including parent company and subsidiaries

Incident History — Conexus Financial (X = Date, Y = Severity)

Conexus Financial cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Media Trust Limited
Incidents

No Incident

https://images.rankiteo.com/companyimages/conexus-financial.jpeg
Conexus Financial
Incidents

No Incident

FAQ

Media Trust Limited company demonstrates a stronger AI Cybersecurity Score compared to Conexus Financial company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Conexus Financial company has disclosed a higher number of cyber incidents compared to Media Trust Limited company.

In the current year, Conexus Financial company and Media Trust Limited company have not reported any cyber incidents.

Neither Conexus Financial company nor Media Trust Limited company has reported experiencing a ransomware attack publicly.

Neither Conexus Financial company nor Media Trust Limited company has reported experiencing a data breach publicly.

Neither Conexus Financial company nor Media Trust Limited company has reported experiencing targeted cyberattacks publicly.

Neither Media Trust Limited company nor Conexus Financial company has reported experiencing or disclosing vulnerabilities publicly.

Neither Media Trust Limited nor Conexus Financial holds any compliance certifications.

Neither company holds any compliance certifications.

Conexus Financial company has more subsidiaries worldwide compared to Media Trust Limited company.

Media Trust Limited company employs more people globally than Conexus Financial company, reflecting its scale as a Book and Periodical Publishing.

Neither Media Trust Limited nor Conexus Financial holds SOC 2 Type 1 certification.

Neither Media Trust Limited nor Conexus Financial holds SOC 2 Type 2 certification.

Neither Media Trust Limited nor Conexus Financial holds ISO 27001 certification.

Neither Media Trust Limited nor Conexus Financial holds PCI DSS certification.

Neither Media Trust Limited nor Conexus Financial holds HIPAA certification.

Neither Media Trust Limited nor Conexus Financial holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Published
Date
2025-11-27
Updated
Date
2025-11-27
Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

Published
Date
2025-11-27
Updated
Date
2025-11-27
Risk Information
cvss3
Base: 9.9
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
References
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

Published
Date
2025-11-27
Updated
Date
2025-11-27
Risk Information
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
References
Description

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References