Comparison Overview
Werth Wealth Management

Werth Wealth Management
1200 Main, 6th Fl, Hays, 67601, US
Last Update: 31/07/2026
WERTH WEALTH MANAGEMENT, LLC is a financial services company based out of 1200 Main St, 6th Fl, Hays Kansas, United States. Raymond James financial advisors may only conduct business with residents of the states and/or jurisdictions for which they are properly register...

Morningstar
22 W. Washington St., Chicago, IL, US, 60602
Last Update: 13/09/2026
Morningstar, Inc. is a leading provider of independent investment insights in North America, Europe, Australia, and Asia. The Company offers an extensive line of products and services for individual investors, financial advisors, asset managers and owners, retirement pl...
Compliance Ranges Comparison

Werth Wealth Management







Morningstar






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
Werth Wealth Management has 42.2% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Morningstar in 2026.
Incident History - Werth Wealth Management (X = Date, Y = Severity)
Werth Wealth Management cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Morningstar (X = Date, Y = Severity)
Morningstar cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Werth Wealth Management

Morningstar
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.