Comparison Overview

STEMER Intellectual Property

VS

Pearse Trust

STEMER Intellectual Property

None, None, Denver, Colorado, US, None
Last Update: 2025-11-25
Between 750 and 799

We are an intellectual property law firm supporting big corporations, start-ups and individuals in the United States and around the world develop and protect their valuable brands. With our comprehensive and integrated legal approach and dedication to collaborative and transparent relationships with our clients, we are your perfect ally.

NAICS: 5411
NAICS Definition: Legal Services
Employees: 1
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Pearse Trust

Pearse Trust Limited, Dublin 18, undefined, D18 F5X2, IE
Last Update: 2025-11-28

We are delighted to share the exciting news that Pearse Trust has been acquired by Hawksford, a global corporate, private client and funds services business. This is a pivotal step for Pearse Trust and we are confident that our clients will welcome this new opportunity to avail of a broader range of services. We are excited about our future as part of the Hawksford family; our shared people and cultural values, dynamic approach to business and client-centric mindset, will provide a world-class professional services organisation for our clients. Read more about the acquisition and the opportunities it brings here: https://lnkd.in/gXxDuAXR

NAICS: 5411
NAICS Definition: Legal Services
Employees: 9
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/stemerlaw.jpeg
STEMER Intellectual Property
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/pearse-trust.jpeg
Pearse Trust
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
STEMER Intellectual Property
100%
Compliance Rate
0/4 Standards Verified
Pearse Trust
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Legal Services Industry Average (This Year)

No incidents recorded for STEMER Intellectual Property in 2025.

Incidents vs Legal Services Industry Average (This Year)

No incidents recorded for Pearse Trust in 2025.

Incident History — STEMER Intellectual Property (X = Date, Y = Severity)

STEMER Intellectual Property cyber incidents detection timeline including parent company and subsidiaries

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

Pearse Trust cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/stemerlaw.jpeg
STEMER Intellectual Property
Incidents

No Incident

https://images.rankiteo.com/companyimages/pearse-trust.jpeg
Pearse Trust
Incidents

No Incident

FAQ

STEMER Intellectual Property company demonstrates a stronger AI Cybersecurity Score compared to Pearse Trust company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Pearse Trust company has disclosed a higher number of cyber incidents compared to STEMER Intellectual Property company.

In the current year, Pearse Trust company and STEMER Intellectual Property company have not reported any cyber incidents.

Neither Pearse Trust company nor STEMER Intellectual Property company has reported experiencing a ransomware attack publicly.

Neither Pearse Trust company nor STEMER Intellectual Property company has reported experiencing a data breach publicly.

Neither Pearse Trust company nor STEMER Intellectual Property company has reported experiencing targeted cyberattacks publicly.

Neither STEMER Intellectual Property company nor Pearse Trust company has reported experiencing or disclosing vulnerabilities publicly.

Neither STEMER Intellectual Property nor Pearse Trust holds any compliance certifications.

Neither company holds any compliance certifications.

Neither STEMER Intellectual Property company nor Pearse Trust company has publicly disclosed detailed information about the number of their subsidiaries.

Pearse Trust company employs more people globally than STEMER Intellectual Property company, reflecting its scale as a Legal Services.

Neither STEMER Intellectual Property nor Pearse Trust holds SOC 2 Type 1 certification.

Neither STEMER Intellectual Property nor Pearse Trust holds SOC 2 Type 2 certification.

Neither STEMER Intellectual Property nor Pearse Trust holds ISO 27001 certification.

Neither STEMER Intellectual Property nor Pearse Trust holds PCI DSS certification.

Neither STEMER Intellectual Property nor Pearse Trust holds HIPAA certification.

Neither STEMER Intellectual Property nor Pearse Trust holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was determined in motogadget mo.lock Ignition Lock up to 20251125. Affected by this vulnerability is an unknown functionality of the component NFC Handler. Executing manipulation can lead to use of hard-coded cryptographic key . The physical device can be targeted for the attack. A high complexity level is associated with this attack. The exploitation appears to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.

Risk Information
cvss2
Base: 1.2
Severity: HIGH
AV:L/AC:H/Au:N/C:P/I:N/A:N
cvss3
Base: 2.0
Severity: HIGH
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
cvss4
Base: 1.0
Severity: HIGH
CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/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
Description

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the interview attachment retrieval endpoint in the Recruitment module serves files based solely on an authenticated session and user-supplied identifiers, without verifying whether the requester has permission to access the associated interview record. Because the server does not perform any recruitment-level authorization checks, an ESS-level user with no access to recruitment workflows can directly request interview attachment URLs and receive the corresponding files. This exposes confidential interview documents—including candidate CVs, evaluations, and supporting files—to unauthorized users. The issue arises from relying on predictable object identifiers and session presence rather than validating the user’s association with the relevant recruitment process. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/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
Description

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the application’s recruitment attachment retrieval endpoint does not enforce the required authorization checks before serving candidate files. Even users restricted to ESS-level access, who have no permission to view the Recruitment module, can directly access candidate attachment URLs. When an authenticated request is made to the attachment endpoint, the system validates the session but does not confirm that the requesting user has the necessary recruitment permissions. As a result, any authenticated user can download CVs and other uploaded documents for arbitrary candidates by issuing direct requests to the attachment endpoint, leading to unauthorized exposure of sensitive applicant data. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/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
Description

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the application does not invalidate existing sessions when a user is disabled or when a password change occurs, allowing active session cookies to remain valid indefinitely. As a result, a disabled user, or an attacker using a compromised account, can continue to access protected pages and perform operations as long as a prior session remains active. Because the server performs no session revocation or session-store cleanup during these critical state changes, disabling an account or updating credentials has no effect on already-established sessions. This makes administrative disable actions ineffective and allows unauthorized users to retain full access even after an account is closed or a password is reset, exposing the system to prolonged unauthorized use and significantly increasing the impact of account takeover scenarios. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/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
Description

OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the password reset workflow does not enforce that the username submitted in the final reset request matches the account for which the reset process was originally initiated. After obtaining a valid reset link for any account they can receive email for, an attacker can alter the username parameter in the final reset request to target a different user. Because the system accepts the supplied username without verification, the attacker can set a new password for any chosen account, including privileged accounts, resulting in full account takeover. This issue has been patched in version 5.8.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/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