Comparison Overview
The Gravity Vault Indoor Rock Gyms

The Gravity Vault Indoor Rock Gyms
1423 Clinton Street, Hoboken, New Jersey, 07030, US
Last Update: 04/02/2026
Lucas Kovalcik and Tim Walsh – avid climbers and entrepreneurial minded – decided to open their first indoor rock gym, called The Gravity Vault, in 2004. Natives of Bergen County, NJ, they knew there was a need for a state-of-the-art climbing gym in the county and wante...

Youngevity International, Inc. (YGYI)
2400 Boswell Road, Chula Vista, 91914, US
Last Update: 28/03/2026
Youngevity International, Inc. (NASDAQ: YGYI) is a fast-growing, innovative, multi-dimensional consumer products company. We offer a wide range of consumer products and services, primarily through person-to-person selling relationships that comprise a “network of networ...
Compliance Ranges Comparison

The Gravity Vault Indoor Rock Gyms







Youngevity International, Inc. (YGYI)






Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for The Gravity Vault Indoor Rock Gyms in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Youngevity International, Inc. (YGYI) in 2026.
Incident History - The Gravity Vault Indoor Rock Gyms (X = Date, Y = Severity)
The Gravity Vault Indoor Rock Gyms cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Youngevity International, Inc. (YGYI) (X = Date, Y = Severity)
Youngevity International, Inc. (YGYI) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

The Gravity Vault Indoor Rock Gyms

Youngevity International, Inc. (YGYI)
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.