Comparison Overview
Up Reply

Up Reply
Luise-Ullrich-Str. 14, Munich, 80636, DE
Last Update: 20/12/2025
Germany based Up Reply is the Reply Group company specialising in digital growth and experience optimisation. The experts provide international clients with data-driven methods for personalisation of digital channels, A/B testing, and analytics across the entire custome...

Hexaware Technologies
#1, Sector III, Millennium Business Park,, 'A' Block , TTC Industrial Estate, Mahape,, Navi Mumbai, Maharashtra, IN, 400710
Last Update: 17/08/2026
At Hexaware, we're not just a global technology and business process services company; we're a community of 31,600+ Hexawarians dedicated to one singular purpose: creating smiles through the power of great people and technology. With a presence in 58 offices across 28 c...
Compliance Ranges Comparison

Up Reply







Hexaware Technologies






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Up Reply in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Hexaware Technologies has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Up Reply (X = Date, Y = Severity)
Up Reply cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hexaware Technologies (X = Date, Y = Severity)
Hexaware Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Up Reply

Hexaware Technologies
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.