Comparison Overview
Forest Electric New Jersey

Forest Electric New Jersey
206 McGaw Dr, Edison, 08837, US
Last Update: 03/12/2025
Forest Electric Corp. is one of the region’s largest single-source providers of complete mission-critical, high-speed data communications and other electrical systems. From design/build through maintenance and service, from residential conversion to tenant buildouts, we...

International Brotherhood of Electrical Workers (IBEW)
900 7th Street, NW, Washington, 20001, US
Last Update: 02/04/2026
The IBEW represents 860,000 active. and retired who work in a wide variety of fields, including utilities, construction, telecommunications, broadcasting, manufacturing, railroads and government. The IBEW has members in both the United States and Canada and stands out ...
Compliance Ranges Comparison

Forest Electric New Jersey







International Brotherhood of Electrical Workers (IBEW)






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Forest Electric New Jersey in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for International Brotherhood of Electrical Workers (IBEW) in 2026.
Incident History - Forest Electric New Jersey (X = Date, Y = Severity)
Forest Electric New Jersey cyber incidents detection timeline including parent company and subsidiaries.
Incident History - International Brotherhood of Electrical Workers (IBEW) (X = Date, Y = Severity)
International Brotherhood of Electrical Workers (IBEW) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Forest Electric New Jersey

International Brotherhood of Electrical Workers (IBEW)
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.