GoQSystem confirms theft of order data affecting 4.37 million people
An intruder exploited a vulnerability in GoQSystem’s contact form and took order data affecting 4,367,390 people across 1,694 merchant companies. The provider removed the form and kept IP restrictions on its admin console.
- Disclosed
- Nov 12, 2026
- Updated Nov 17, 2026
- Severity
- Septic Tank Blew
- No CVE: a breach, not a bug
- Splash zone
- Buyers and recipients whose orders were held in the affected GoQSystem merchant accounts. Older orders are also in scope.
- GoQSystem · SaaS · Ecommerce · Data breach
- In the wild
- Yes
- GoQSystem confirmed contact-form exploitation and order data theft.
What happened
GoQSystem centralizes order processing for online merchants. GoQSystem traced the intrusion to a vulnerability in its contact form. Its reports give no further exploit details. The provider removed the form and says admin-console IP restrictions will remain in effect while it validates security.
The stolen data includes buyer and recipient names, addresses, phone numbers, email addresses and order details. The affected orders include records from before the November 10–11 intrusion. GoQSystem does not hold credit card data and excluded it from the leak. The November 13 totals count companies, orders and individuals separately. The provider planned to send affected merchants download instructions on November 14–15.
The first notice reported no further intrusion or known misuse at that time. The later impersonation warning gives no evidence of an active fake-site campaign. Buyers and recipients can verify whether their order was affected through the merchant’s established contact channel.
Follow the current partner API status. For BASE merchants, GoQSystem now says there are no further actions. Rakuten merchants should update their license key, and STORES merchants should reissue refresh tokens for order management and inventory. Handle pending GoQ Logi FBA requests in Amazon Seller Central while the integration remains paused.
Crime-scene timeline
Nov 10–11, 2026
Intruder accesses the order-management system
GoQSystem blocks the access route and temporarily suspends the service on November 11.
Nov 12, 2026
GoQSystem confirms order data theft
Emergency measures let the provider reopen the service with access limited by connection source.
Nov 13, 2026
GoQSystem identifies the entry point and scope
A vulnerable contact form was exploited and has been removed. The provider counts 4,984,595 affected orders across 1,694 companies and 4,367,390 people.
Nov 14, 2026
Provider lists integrations that require merchant action
Its status table marks Rakuten, BASE and STORES as requiring action and GoQ Logi as partially suspended.
Nov 15, 2026
GoQSystem warns of impersonation
The provider publishes its genuine domains and says it has no confirmed cases of harm from lookalike sites at the time of the notice.
Nov 17, 2026
BASE API integration returns
GoQSystem says no further steps are required for BASE merchants. Rakuten and STORES still require action, and the GoQ Logi FBA integration remains paused.
Who said what
We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.
- GoQSystem November 12 incident noticePrimaryConfirms intrusion, extraction, data fields and restricted service recovery.
- GoQSystem November 13 scope and responsePrimaryGives affected companies, orders and people, identifies the vulnerable form and describes merchant response.
- GoQSystem API connection statusPrimaryLists partner status and merchant recovery steps.
- GoQSystem November 15 impersonation warningPrimaryLists genuine login domains and steps for reporting or responding to lookalikes.