Comparison Overview

Lawrie

VS

Morae

Lawrie

310 St Vincent Street, Glasgow, Scotland, G2 5RG, GB
Last Update: 2025-11-28
Between 700 and 749

Companies don't always get clear and easy to digest guidance on how best to protect and manage their IP. This can prevent businesses from reaching their full potential. At Lawrie, we understand that pain. We know that IP can be a difficult part of an organisation's growth strategy. But we also know that - when managed properly - it can completely transform the success of a business. So, our mission is simple - to be the easiest intellectual property team to work with. We provide a pain-free IP service with clarity and direction, enabling clients to confidently secure a market-leading position and build a better tomorrow. Lawrie - The Intellectual Property team for dynamic brands and forward-thinking minds.

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

Morae

811 Louisiana Street, Houston, TX, 77002, US
Last Update: 2025-11-27
Between 750 and 799

Morae Global Corporation ("Morae") is trusted around the world for the delivery of digital and business solutions for a constantly changing legal industry. Founded in 2015, Morae has earned wide respect for the expertise and experience of our legal consulting, technology, and operations professionals, many of whom have in-house legal, law firm, or other relevant industry experience. We strive to make a difference every day for our law firm and legal department clients by collaborating closely with them to develop strategy, implement meaningful change, and achieve the business objectives they care about most. This includes offering clients the right people and technology they need to efficiently meet their contracts, discovery, information, and resourcing goals.

NAICS: 5411
NAICS Definition: Legal Services
Employees: 1,004
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/lawrie-intellectual-property.jpeg
Lawrie
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/morae-legal.jpeg
Morae
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
Lawrie
100%
Compliance Rate
0/4 Standards Verified
Morae
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Legal Services Industry Average (This Year)

No incidents recorded for Lawrie in 2025.

Incidents vs Legal Services Industry Average (This Year)

No incidents recorded for Morae in 2025.

Incident History — Lawrie (X = Date, Y = Severity)

Lawrie cyber incidents detection timeline including parent company and subsidiaries

Incident History — Morae (X = Date, Y = Severity)

Morae cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/lawrie-intellectual-property.jpeg
Lawrie
Incidents

No Incident

https://images.rankiteo.com/companyimages/morae-legal.jpeg
Morae
Incidents

No Incident

FAQ

Morae company demonstrates a stronger AI Cybersecurity Score compared to Lawrie company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Morae company has disclosed a higher number of cyber incidents compared to Lawrie company.

In the current year, Morae company and Lawrie company have not reported any cyber incidents.

Neither Morae company nor Lawrie company has reported experiencing a ransomware attack publicly.

Neither Morae company nor Lawrie company has reported experiencing a data breach publicly.

Neither Morae company nor Lawrie company has reported experiencing targeted cyberattacks publicly.

Neither Lawrie company nor Morae company has reported experiencing or disclosing vulnerabilities publicly.

Neither Lawrie nor Morae holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Lawrie company nor Morae company has publicly disclosed detailed information about the number of their subsidiaries.

Morae company employs more people globally than Lawrie company, reflecting its scale as a Legal Services.

Neither Lawrie nor Morae holds SOC 2 Type 1 certification.

Neither Lawrie nor Morae holds SOC 2 Type 2 certification.

Neither Lawrie nor Morae holds ISO 27001 certification.

Neither Lawrie nor Morae holds PCI DSS certification.

Neither Lawrie nor Morae holds HIPAA certification.

Neither Lawrie nor Morae 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