Comparison Overview
Burlington Stores, Inc.

Burlington Stores, Inc.
2006 Route 130, Burlington, NJ, US, 08016
Last Update: 01/04/2026
Burlington Stores, Inc., headquartered in New Jersey, is a nationally recognized off-price retailer. Burlington is a Fortune 500 company and its common stock is traded on the New York Stock Exchange under the ticker symbol “BURL.” The Company operates more than 1000 sto...

ZARA
Arteixo, A Coruña, ES, 15143
Last Update: 31/05/2026
Zara is a forward-thinking force in fashion; embodying what is possible when responsibility and aspiration are accessible to all. By bringing more thoughtful style to the world, we aim to provide everyone, no matter where they are, with the inspiringly beautiful, always...
Compliance Ranges Comparison

Burlington Stores, Inc.







ZARA






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Burlington Stores, Inc. in 2026.
Incidents vs Retail Industry Avg (This Year)
ZARA has 177.78% more incidents than the average of all companies with at least one recorded incident.
Incident History - Burlington Stores, Inc. (X = Date, Y = Severity)
Burlington Stores, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ZARA (X = Date, Y = Severity)
ZARA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Burlington Stores, Inc.

ZARA
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.