Comparison Overview
良品計画(MUJI)

良品計画(MUJI)
2-5-1 Koraku,, Bunkyo-ku, 112-0004, JP
Last Update: 01/04/2026
1980年12月、西友ストアー(現:合同会社西友)のプライベートブランドとして40品目でデビューした「無印良品」は、現在では約7,500品目、店舗は日本を含む29の国・地域へと広がりました。 1989年に設立した良品計画は、「無印良品」の企画開発から、商品調達、流通・販売までを行う製造小売業です。他にも「Café&Meal MUJI」「IDÉE」の展開、キャンプ場の運営などを行っています。 「人と自然とモノの望ましい関係と心豊かな人間社会」を考えた商品、サービス、店舗、活動を通じて「感じ良い暮らしと社会」の実現に貢献することを企業理...

IKEA
Olof Palmestraat 1, Delft, Zuid-Holland, NL, 2616
Last Update: 02/06/2026
The IKEA vision is to create a better everyday life for the many people. Our business idea is to offer well-designed, functional and affordable, high-quality home furnishing, produced with care for people and the environment. The IKEA Brand unites more than 200.000 co-...
Compliance Ranges Comparison

良品計画(MUJI)







IKEA






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for 良品計画(MUJI) in 2026.
Incidents vs Retail Industry Avg (This Year)
IKEA has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - 良品計画(MUJI) (X = Date, Y = Severity)
良品計画(MUJI) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IKEA (X = Date, Y = Severity)
IKEA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

良品計画(MUJI)

IKEA
FAQ
Latest Global CVEs
PlaywrightCapture stored capture-specific configuration and runtime data as mutable class-level variables rather than instance-level variables. Consequently, multiple Capture objects running within the same Python process could share state, including HTTP headers, cookies, browser storage, HTTP credentials, proxy configuration, user-agent settings, geolocation information, and captured request data. In a multi-user or concurrent deployment, information supplied during one capture could therefore persist and be reused by a subsequent or parallel capture. This could result in the disclosure of authentication cookies, credentials, browser storage, or captured request data belonging to another user. It could also cause requests to be performed with another capture's authentication context, headers, or proxy configuration, potentially enabling unauthorized access to remote resources or interference with other capture operations. The vulnerability is resolved by initializing all capture-specific settings and request data as instance variables in the Capture constructor, ensuring that state is isolated between capture operations.
Anubis is a Web AI Firewall Utility that challenges users' connections in order to protect upstream resources from scraper bots. From 1.22.0 until 1.26.0-pre1, lib/policy/checker.go PathChecker.Check() trusted the client-controlled X-Original-URI header before matching r.URL.Path, allowing an HTTP client to match default data/common/keep-internet-working.yaml ALLOW rules such as ^/\.well-known/.*$ and bypass the Anubis challenge. This issue is fixed in version 1.26.0-pre1.
Wekan is open source kanban built with Meteor. Prior to 9.46, header-login with HEADER_LOGIN_TRUSTED_IPS uses getRequestIp() in server/lib/headerLoginAuth.js to trust the client-supplied X-Forwarded-For header before the real socket address, allowing an unauthenticated attacker to send HEADER_LOGIN_ID for any username and receive a meteor_login_token session, including for admin. This issue is fixed in version 9.46.
MaaAssistantArknights is a one-click tool for daily Arknights tasks. In the current dev-v2 workflow, .github/workflows/release-preparation.yml inlined attacker-controlled github.event.pull_request.title into a run: shell command during the pull_request opened, reopened, and ready_for_review events, so a non-draft fork PR whose title starts with Release v could execute shell commands on the ubuntu-latest runner during the generate-changelog job. This vulnerability is fixed by commit cafc3946059e6337d2089d4fec8b6885ba17c332.
Qinglong is a timed task management platform supporting Python3, JavaScript, Shell, and Typescript. Prior to 2.20.1, the init guard middleware in back/loaders/express.ts checks /api/user/init but not /open/user/init, while rewrite('/open/*', '/api/$1') rewrites the whitelisted /open/* path after JWT authentication and the guard have passed; an unauthenticated attacker can send PUT /open/user/init to reset administrator credentials on an initialized instance. This issue is fixed in 2.20.1.