Comparison Overview
Wharton Executive Education | Behavioral Economics: Consumer Choice and Decision Making
Wharton Executive Education | Behavioral Economics: Consumer Choice and Decision Making
Philadelphia, US
Last Update: 16/12/2025
By leveraging the psychological drivers behind consumer behavior, leaders are enhancing the ability to predict consumer and employee decision making. In fact, as per a report by EY, investment in the behavioral economy has increased by approximately 146 percent in the l...
University of Houston
4300 Martin Luther King Blvd, Houston, TX, US, 77204
Last Update: 01/04/2026
Founded in 1927, the University of Houston is the leading public research university in the vibrant international city of Houston. Each year, we educate more than 47,000 students in more than 250 undergraduate and graduate academic programs, on campus and online. UH awa...
Compliance Ranges Comparison
Wharton Executive Education | Behavioral Economics: Consumer Choice and Decision Making
University of Houston
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Wharton Executive Education | Behavioral Economics: Consumer Choice and Decision Making in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Houston in 2026.
Incident History - Wharton Executive Education | Behavioral Economics: Consumer Choice and Decision Making (X = Date, Y = Severity)
Wharton Executive Education | Behavioral Economics: Consumer Choice and Decision Making cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Houston (X = Date, Y = Severity)
University of Houston cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Wharton Executive Education | Behavioral Economics: Consumer Choice and Decision Making
University of Houston
FAQ
Latest Global CVEs
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/handler.go sendFile handler opened files using a cleaned path but derived the authorization filename from raw req.URL.Path, so a trailing slash could bypass .goshs ACL-file protection and block-list checks. This issue is fixed in version 2.1.5.
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.5, the httpserver/updown.go multipart upload handler split part.FileName() on / but did not reject .., allowing an unauthenticated upload with filename .. to create a file outside the served tree. This issue is fixed in version 2.1.5.
goshs is a feature-rich single-binary file server for red teamers and developers. Prior to 2.1.4, the httpserver/server.go wdGuard handled WebDAV MOVE as a write-only method and did not enforce --no-delete, allowing WebDAV clients to delete or overwrite files via MOVE with Overwrite: T. This issue is fixed in version 2.1.4.
goshs is a feature-rich single-binary file server for red teamers and developers. From 2.1.3 until 2.1.4, the sftpserver/sftpserver.go password handler used Username != "" && Password != "", so running goshs with -b 'admin:' -sftp and no -fkf left both SFTP authentication handlers unset and allowed unauthenticated file access. This issue is fixed in version 2.1.4.
Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, HttpPostRequestEncoder constructs multipart HTTP request bodies by directly concatenating user-supplied filenames and field names into Content-Disposition MIME headers without validating or sanitizing CRLF characters (\r\n). Since MIME headers are delimited by CRLF, an attacker who controls the filename can inject arbitrary MIME headers into the multipart body part. The root cause is that neither the encoder nor the FileUpload implementations' setFilename() methods, which only check for null, neutralize CRLF characters before the filename is embedded into the header. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.