Comparison Overview
Be-Mobile

Be-Mobile
Kardinaal Mercierlaan 1A, Melle, 9090, BE
Last Update: 01/05/2026
Be-Mobile is a smart mobility service provider, headquartered in Ghent, Belgium. Leveraging its expertise, Be-Mobile develops high-tech solutions in the areas of smart mobility, traffic monitoring and management, connected vehicle technologies, traffic information, mobi...

Reply
C.so Francia, 110, Turin, 10143, IT
Last Update: 02/04/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

Be-Mobile







Reply






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Be-Mobile in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Reply in 2026.
Incident History - Be-Mobile (X = Date, Y = Severity)
Be-Mobile 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

Be-Mobile

Reply
FAQ
Latest Global CVEs
A weakness has been identified in PHPGurukul Student Information System 1.0. Affected by this vulnerability is an unknown functionality of the file /student_edit1.php. Executing a manipulation of the argument ID can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks.
A vulnerability has been found in macrozheng mall up to 1.0.3. The affected element is an unknown function of the file /order/paySuccess of the component Payment Status Endpoint. The manipulation of the argument orderId leads to enforcement of behavioral workflow. The attack is possible to be carried out remotely. The vendor deleted the GitHub issue for this vulnerability without any explanation.
A security flaw has been discovered in itsourcecode Sales and Inventory System 1.0. Impacted is an unknown function of the file /pages/emp_del.php. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.
A vulnerability was identified in itsourcecode Sales and Inventory System 1.0. This issue affects some unknown processing of the file /pages/emp_edit.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotely. The exploit is publicly available and might be used.
The Custom User Registration Fields for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 2.2.3. This is due to the plugin accepting an attacker-controlled afreg_select_user_role value from the unauthenticated WooCommerce Store API /wc/store/v1/checkout request in the af_reg_checkout_data_to_order_meta_data_block() function, persisting it in order meta, and then passing it directly to WP_User::add_role() in the af_reg_custom_order_processing_function() function (hooked to woocommerce_thankyou) without validating against the plugin's admin-configured allowed role list. This makes it possible for unauthenticated attackers to elevate their privileges to Administrator by creating an account during checkout with a modified JSON body specifying administrator (or any other role slug) as the desired role. Note: The exploit requires the "User Role Selection" setting to be enabled.