Comparison Overview
Grav Web Solution Pvt. Ltd
Grav Web Solution Pvt. Ltd
Noida, Uttar Pradesh, IN, 201309
Last Update: 22/09/2026
A purpose-led organization that is building a meaningful future through innovation, technology, and collective knowledge. We're #Buildingoncareer. GRAV WEB SOLUTION's proactive stance on climate change and award winning work with communities across the world have earn...
Reply
C.so Francia, 110, Turin, 10143, IT
Last Update: 09/09/2026
Reply [EXM, STAR: REY] specialises in the design and implementation of solutions based on new communication channels and digital media. As a network of highly specialised companies, Reply defines and develops business models enabled by the new models of AI, big data, cl...
Compliance Ranges Comparison
Grav Web Solution Pvt. Ltd
Reply
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Grav Web Solution Pvt. Ltd has 32.89% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Reply in 2026.
Incident History - Grav Web Solution Pvt. Ltd (X = Date, Y = Severity)
Grav Web Solution Pvt. Ltd cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Reply (X = Date, Y = Severity)
Reply cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Grav Web Solution Pvt. Ltd
Reply
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)