Comparison Overview
Lipsy London

Lipsy London
200-208 Tottenham Court Road, London, W1T 7PL, GB
Last Update: 15/12/2025
Lipsy is now part of NEXT Wholly Owned Brands. You can find out more about our culture, opportunities and brands on NEXT Wholly Owned Brands LinkedIn Page. See you there!

Old Navy
2 Folsom Street, San Francisco, 94158, US
Last Update: 14/09/2026
Forget what you know about old-school industry rules. When you work at Old Navy, you’re choosing a different path. From day one, we’ve been on a mission to democratize fashion and make shopping fun again. Our teams make style accessible to everyone, creating high-qualit...
Compliance Ranges Comparison

Lipsy London







Old Navy






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Lipsy London in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Old Navy in 2026.
Incident History - Lipsy London (X = Date, Y = Severity)
Lipsy London cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Old Navy (X = Date, Y = Severity)
Old Navy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Lipsy London

Old Navy
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)