Sheridan Junior High School
Last Update: 2025-03-09 (UTC)
Between 800 and 900
Strong
None
NAICS: 52
NAICS Definition:
Employees: 6
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
Comparison Overview
Sheridan Junior High School
VS
Fidelity National Financial
Fidelity National Financial
Last Update: 2025-08-21 (UTC)
Strong
Between 800 and 900
Fidelity National Financial, Inc. (NYSE: FNF) is a leading provider of title insurance and transaction services to the real estate and mortgage industries. Ranked #359 on the FORTUNE 500(r) list for 2023, FNF is the nation's largest title insurance company through our title insurance underwriters (Fidelity National Title, Chicago Title, Commonwealth Land Title, Alamo Title and National Title Insurance of New York) that collectively issue more title insurance policies than any other title company in the United States. Our mission is to advance, expand, and protect the experience of property ownership by making the safety of our customers our primary focus. We pride ourselves on being extremely customer-oriented, motivated, and quick to provide solutions for all of your title insurance needs. We strongly encourage employee ownership of company stock so our FNF family can share in our company’s continuous growth and be a valuable part of something bigger than themselves.
NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 19,501
Subsidiaries: 0
12-month incidents
0
Known data breaches
3
Attack type number
1
Compliance Badges Comparison
Security & Compliance Standards Overview
Sheridan Junior High School
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
Fidelity National Financial
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
Compliance Summary
Sheridan Junior High School
100%
Compliance Rate
0/4 Standards Verified
Fidelity National Financial
0%
Compliance Rate
0/4 Standards Verified
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Average (This Year)
No incidents recorded for Sheridan Junior High School in 2025.
Incidents vs Financial Services Industry Average (This Year)
No incidents recorded for Fidelity National Financial in 2025.
Incident History — Sheridan Junior High School (X = Date, Y = Severity)
Sheridan Junior High School cyber incidents detection timeline including parent company and subsidiaries
Incident History — Fidelity National Financial (X = Date, Y = Severity)
Fidelity National Financial cyber incidents detection timeline including parent company and subsidiaries
FAQ
Both Sheridan Junior High School company and Fidelity National Financial company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.
Fidelity National Financial company has historically faced a number of disclosed cyber incidents, whereas Sheridan Junior High School company has not reported any.
In the current year, Fidelity National Financial company and Sheridan Junior High School company have not reported any cyber incidents.
Neither Fidelity National Financial company nor Sheridan Junior High School company has reported experiencing a ransomware attack publicly.
Fidelity National Financial company has disclosed at least one data breach, while Sheridan Junior High School company has not reported such incidents publicly.
Neither Fidelity National Financial company nor Sheridan Junior High School company has reported experiencing targeted cyberattacks publicly.
Neither Sheridan Junior High School company nor Fidelity National Financial company has reported experiencing or disclosing vulnerabilities publicly.
Neither Sheridan Junior High School company nor Fidelity National Financial company has publicly disclosed detailed information about the number of their subsidiaries.
Fidelity National Financial company employs more people globally than Sheridan Junior High School company, reflecting its scale as a Financial Services.
Latest Global CVEs (Not Company-Specific)
Description
FreshRSS is a free, self-hostable RSS aggregator. Versions 1.26.3 and below do not sanitize certain event handler attributes in feed content, so by finding a page that renders feed entries without CSP, it is possible to execute an XSS payload. The Allow API access authentication setting needs to be enabled by the instance administrator beforehand for the attack to work as it relies on api/query.php. An account takeover is possible by sending a change password request via the XSS payload / setting UserJS for persistence / stealing the autofill password / displaying a phishing page with a spoofed URL using history.replaceState() If the victim is an administrator, the attacker can also perform administrative actions. This issue is fixed in version 1.27.0.
Risk Information
cvss3
Base: 6.7
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L
Description
go-f3 is a Golang implementation of Fast Finality for Filecoin (F3). In versions 0.8.6 and below, go-f3 panics when it validates a "poison" messages causing Filecoin nodes consuming F3 messages to become vulnerable. A "poison" message can can cause integer overflow in the signer index validation, which can cause the whole node to crash. These malicious messages aren't self-propagating since the bug is in the validator. An attacker needs to directly send the message to all targets. This issue is fixed in version 0.8.7.
Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description
go-f3 is a Golang implementation of Fast Finality for Filecoin (F3). In versions 0.8.8 and below, go-f3's justification verification caching mechanism has a vulnerability where verification results are cached without properly considering the context of the message. An attacker can bypass justification verification by submitting a valid message with a correct justification and then reusing the same cached justification in contexts where it would normally be invalid. This occurs because the cached verification does not properly validate the relationship between the justification and the specific message context it's being used with. This issue is fixed in version 0.8.9.
Risk Information
cvss3
Base: 5.9
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L
Description
mkdocs-include-markdown-plugin is an Mkdocs Markdown includer plugin. In versions 7.1.7 and below, there is a vulnerability where unvalidated input can collide with substitution placeholders. This issue is fixed in version 7.1.8.
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
References
- https://github.com/mondeja/mkdocs-include-markdown-plugin/commit/7466d67aa0de8ffbc427204ad2475fed07678915
- https://github.com/mondeja/mkdocs-include-markdown-plugin/issues/274
- https://github.com/mondeja/mkdocs-include-markdown-plugin/pull/277
- https://github.com/mondeja/mkdocs-include-markdown-plugin/security/advisories/GHSA-v39m-5m9j-m9w9
Description
go-mail is a comprehensive library for sending mails with Go. In versions 0.7.0 and below, due to incorrect handling of the mail.Address values when a sender- or recipient address is passed to the corresponding MAIL FROM or RCPT TO commands of the SMTP client, there is a possibility of wrong address routing or even ESMTP parameter smuggling. For successful exploitation, it is required that the user's code allows for arbitrary mail address input (i. e. through a web form or similar). If only static mail addresses are used (i. e. in a config file) and the mail addresses in use do not consist of quoted local parts, this should not affect users. This issue is fixed in version 0.7.1
Risk Information
cvss4
Base: 8.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/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
