Comparison Overview
Georgia Association for Women in Higher Education (GAWHE)

Georgia Association for Women in Higher Education (GAWHE)
Atlanta, US
Last Update: 03/03/2026
The Georgia Association for Women in Higher Education is dedicated to providing professional support for women in higher education organizations through networking, professional development, advocacy, and publications. The Association is part of the ACE Women’s Network...

YMCA of the USA
101 N. Wacker Dr, Chicago, IL, US, 60606
Last Update: 04/04/2026
YMCA of the USA is the national resource office for the nation's YMCAs. Located in Chicago, IL, YMCA of the USA exists to serve YMCAs. To address the specific needs of communities, each YMCA is an independent organization, autonomous and separate from YMCA of the USA. T...
Compliance Ranges Comparison

Georgia Association for Women in Higher Education (GAWHE)







YMCA of the USA






Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for Georgia Association for Women in Higher Education (GAWHE) in 2026.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for YMCA of the USA in 2026.
Incident History - Georgia Association for Women in Higher Education (GAWHE) (X = Date, Y = Severity)
Georgia Association for Women in Higher Education (GAWHE) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - YMCA of the USA (X = Date, Y = Severity)
YMCA of the USA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Georgia Association for Women in Higher Education (GAWHE)

YMCA of the USA
FAQ
Latest Global CVEs
GNU Savannah Administration Savane through 3.17 uses untrusted data as part of authorization.
- https://cgit.git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/file.php?h=release-3.17#n113
- https://cgit.git.savannah.gnu.org/cgit/administration/savane.git/tree/frontend/php/file.php?h=release-3.17#n123
- https://news.ycombinator.com/item?id=48605220
- https://www.fsf.org/news/statement-regarding-gnu-savannah-security-reports
- https://www.hacktron.ai
- https://www.mallory.ai/stories/019ee445-bdd4-7775-93b5-a8faaf5c2eb7
AVideo TopMenu plugin through version 26.0 contains a stored cross-site scripting vulnerability in menu item rendering due to missing output encoding of icon classes, URLs, and text labels. Attackers can inject malicious JavaScript through unescaped menu item fields that execute for all site visitors, potentially stealing session cookies or performing unauthorized actions.
AVideo through version 25.0 contains an authentication bypass vulnerability in the decryptMessage.json.php endpoint that allows unauthenticated users to decrypt PGP messages. Remote attackers can submit private keys, ciphertext, and passphrases to perform server-side decryption without credentials, exposing key material to logs and enabling resource exhaustion attacks.
AVideo through 29.0 contains an authorization bypass vulnerability in the Meet plugin's uploadRecordedVideo.json.php endpoint that derives the target users_id from the uploaded filename without verification. An attacker with knowledge of the Meet shared secret can craft a malicious file upload with a filename containing an arbitrary users_id to invoke passwordless User->login() and establish an authenticated session as any user including admin. Attackers can obtain the Meet shared secret through path-traversal vulnerabilities or timing attacks against checkToken.json.php, then POST a crafted file to uploadRecordedVideo.json.php with a filename like '1-anything.mp4' to hijack admin sessions and gain full account takeover.
AVideo through version 27.0 contains a server-side request forgery vulnerability in plugin/Live/test.php that allows authenticated administrators to read arbitrary URLs via the statsURL parameter, which lacks isSSRFSafeURL() validation and accepts requests to private IP ranges and cloud metadata endpoints. Attackers can exploit this by crafting requests to internal services, cloud metadata endpoints like 169.254.169.254, and localhost to retrieve sensitive information including IAM credentials, internal service responses, and network configuration details.