Comparison Overview

UBTech Conference

VS

Pacific Horticulture

UBTech Conference

35 Nutmeg Drive , Trumbull, 06611, US
Last Update: 2025-11-22
View Profile
Between 750 and 799
http://ubtechconference.com

At the annual UBTech conference, higher education technology professionals discover new strategies and tools to drive success in student achievement, enrollment and operational efficiency. For campus IT and AV managers and their teams, UBTech provides an unparalleled opportunity to learn and network with peers and to connect with solution providers dedicated to helping campus leaders translate new strategies into action. Watch the video to learn more: https://youtu.be/RN6l93wTbm0 Join the UBTech community June 4-6, 2018 at the Mirage, Las Vegas. Register at ubtechconference.com

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

Pacific Horticulture

PO Box 5995, Berkeley, CA, 94705, US
Last Update: 2025-11-26
Between 750 and 799
https://www.pacifichorticulture.org/

Pacific Horticulture provides science-based climate solutions that elevate the role of horticulture to build a resilient future. Our learning offerings address local and regional practices applicable to home and community gardens, developed landscapes and ecological restorations. Programs demonstrate what beautifully designed climate-appropriate gardens and landscapes can be at every scale. We serve the Pacific Region including Alaska, Baja California, British Columbia, California, Hawaii, Oregon, Washington.

NAICS: 511
NAICS Definition:
Employees: 6
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ubtech.jpeg
UBTech Conference
—
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/pacific-horticulture-society.jpeg
Pacific Horticulture
—
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
UBTech Conference
100%
Compliance Rate
0/4 Standards Verified
Pacific Horticulture
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 UBTech Conference in 2025.

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

No incidents recorded for Pacific Horticulture in 2025.

Incident History — UBTech Conference (X = Date, Y = Severity)

UBTech Conference cyber incidents detection timeline including parent company and subsidiaries

Incident History — Pacific Horticulture (X = Date, Y = Severity)

Pacific Horticulture cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ubtech.jpeg
UBTech Conference
Incidents

No Incident

https://images.rankiteo.com/companyimages/pacific-horticulture-society.jpeg
Pacific Horticulture
Incidents

No Incident

FAQ

UBTech Conference company demonstrates a stronger AI Cybersecurity Score compared to Pacific Horticulture company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Pacific Horticulture company has disclosed a higher number of cyber incidents compared to UBTech Conference company.

In the current year, Pacific Horticulture company and UBTech Conference company have not reported any cyber incidents.

Neither Pacific Horticulture company nor UBTech Conference company has reported experiencing a ransomware attack publicly.

Neither Pacific Horticulture company nor UBTech Conference company has reported experiencing a data breach publicly.

Neither Pacific Horticulture company nor UBTech Conference company has reported experiencing targeted cyberattacks publicly.

Neither UBTech Conference company nor Pacific Horticulture company has reported experiencing or disclosing vulnerabilities publicly.

Neither UBTech Conference nor Pacific Horticulture holds any compliance certifications.

Neither company holds any compliance certifications.

UBTech Conference company has more subsidiaries worldwide compared to Pacific Horticulture company.

Neither UBTech Conference nor Pacific Horticulture holds SOC 2 Type 1 certification.

Neither UBTech Conference nor Pacific Horticulture holds SOC 2 Type 2 certification.

Neither UBTech Conference nor Pacific Horticulture holds ISO 27001 certification.

Neither UBTech Conference nor Pacific Horticulture holds PCI DSS certification.

Neither UBTech Conference nor Pacific Horticulture holds HIPAA certification.

Neither UBTech Conference nor Pacific Horticulture 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