Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
An online shop holds customer names, addresses and email addresses, and in some cases card data. If the checkout is tampered with or data leaks, the harm reaches customers first and then the shop's reputation. This page is for operators of EC-CUBE, WooCommerce, Shopify and similar shops, and for companies that run a shop they built themselves. It sets out what we check, how, what you receive and what it costs.
Cyber Shield changes the shape of the assessment to match your platform. A CMS-based shop starts from JPY 49,800 (excl. tax). A custom-built shop is assessed as a web application, from JPY 98,000 (excl. tax).
Why are e-commerce sites targeted so often?
Customer personal data and card data meet in one place. Shops that run the same platform, such as EC-CUBE, also share its weak points, so one flaw that is found puts all of those shops in view.
Two cases show how this plays out. In December 2019, IPA warned that the payment pages of sites built with EC-CUBE had been rewritten and that about 140,000 card records had leaked. On 14 October 2026, JVN published a flaw in the official Amazon Pay plugin for EC-CUBE 4, tracked as CVE-2026-103671. The developer has confirmed that attacks using it have already happened.
IPA also surveyed 20 e-commerce operators that had recently suffered damage. Of them, 75% had not fixed vulnerabilities in their site programs or CMS, and 90% had taken no measures for the operation phase. The pattern points to gaps in upkeep after launch.
What does an e-commerce assessment cover?
The weak spots differ by the place where information moves. The table below lists where we look, in everyday terms. Test procedures and attack strings stay unpublished.
| Where we look | What we confirm | What can happen if there is a hole |
|---|---|---|
| The path to payment | Whether price, quantity and destination can be changed along the way | Purchase at a false low price, or a visitor sent to a fake page |
| Login and member screens | Whether one member can open another member's data or order history without rights | Customer data leaks, or someone is impersonated |
| Admin screen | Whether non-admins are kept out and no weak authentication remains | Products or prices rewritten, or an unwanted admin added |
| CMS core and extensions | Whether outdated or unused parts are left behind | A weakness that is already public gets used as it is |
| External parts loaded on a page | Whether a payment page loads scripts of unknown origin | Card numbers are skimmed |
| Settings and records | Whether default settings remain and whether a record would show something odd | Damage is noticed late |
For the mechanics of individual flaws, see card skimming, EC-CUBE vulnerabilities and WooCommerce vulnerabilities.
What this assessment does not cover
The payment page run by a payment service provider, the outside company that handles card payments, is not something we can assess. Server settings are a separate server and network assessment, and the inside of a smartphone app is a separate smartphone app assessment. An API on its own goes to the API assessment.
How do tools and people divide the work?
The work has two stages. A tool scan comes first, and then a person reviews the results. We do not stop at the tool because a shop has a purchase flow, and a machine cannot read what that flow means.
Tools apply one standard to every page. Old parts, transport settings and known weaknesses come out quickly. A person then reads each finding, decides whether it is a real problem and removes false positives.
After that, the person registers as a member, puts items in the cart and works through the steps up to the point of purchase. Two examples: can member A open member B's order history, and is there a loophole in how a coupon or shipping fee is calculated?
Before the work starts, a consent form fixes the target URLs, the period and the methods in writing. Testing a site without permission may break Japan's Unauthorized Computer Access Law.
What do you receive when the assessment ends?
You receive a report in Japanese. For each hole it states which screen and which part is affected, what happens if you leave it, and how to fix it. It is written so that a non-technical shop manager can read it, with enough detail to hand to your developer.
Once you have fixed the holes, one re-assessment is free. We confirm that each repaired spot is now closed and add the outcome to your report.
The METI and IPA guidelines for e-commerce sites set 14 requirements for the build phase and 7 for the operation phase, ranked as required, necessary or recommended. Ranking the report's findings against this framework can help you set priorities and a budget.
What does it cost, and what changes the amount?
Which assessment you need depends on how the shop is built. All amounts exclude tax.
| Shop type | Assessment | Price | Range |
|---|---|---|---|
| CMS-based, such as EC-CUBE or WooCommerce | WordPress/CMS site assessment | from JPY 49,800 (excl. tax) | up to 30 pages |
| Custom-built | Web application assessment Lite | from JPY 98,000 (excl. tax) | up to 10 screens |
| Custom-built | Web application assessment Standard | from JPY 198,000 (excl. tax) | up to 20 screens, with manual checks that include screens behind login |
| Beyond the range | Additional screen | from JPY 10,000 per screen (excl. tax) | per screen |
Each assessment includes a report and one re-assessment after the fixes.
Three things raise the amount. The first is the number of pages or screens. The second is how much sits behind login, such as member and admin screens. The third is the number of extensions installed. A purchase flow usually needs a login to test, so for a custom-built shop we may recommend Standard, where a person checks the screens behind login by hand.
The formal quotation follows the free assessment. For a first look at what outsiders can see, run the free URL check. If you are not sure which row fits, contact us with the name of the platform you run. The pricing page lists every amount in one place.
How does a request go from first contact to delivery?
This is the general flow from first contact to after-delivery support, with the points specific to a shop added.
- In the free consultation we ask about the platform (EC-CUBE, WooCommerce, custom-built or other) and the payment method.
- Before anything starts, both sides sign a non-disclosure agreement (NDA), free of charge.
- You sign the consent form, and we run the free assessment (a quick scan with a person's review) and give you an issue report.
- We price the repair of what the assessment found.
- Once you order, every item is assessed and the holes are closed.
- Before delivery you get a PDF that explains each change.
- You check the order flow on the real screens.
- We deliver. Support is free for the first month afterwards.
To keep parts updated and watch for tampering after delivery, see the maintenance and advisory plans.
Common objections
What if the shop may already have been attacked?
Confirming the damage and stopping it come before an assessment. If anything rings a bell, read the emergency guide. Recovery from tampering or malware is from JPY 29,800 (excl. tax). Afterwards, an assessment checks whether the hole that let the attacker in is still open.
We leave card payment to an outside service, so does this concern us?
It still does. Even with no card numbers on your side, the area around the screen that leads to payment can be rewritten, and visitors can be sent to a fake input field. Customer names, addresses and order history sit in your own database.
Separating what the payment provider covers from what stays with you also narrows the scope of an assessment.
We use the official plugin, so is that not safe?
An official plugin can also have a hole. The Amazon Pay plugin case above is one example. What matters is knowing which parts are installed and which version each one is, so that you can apply a fixed version as soon as it appears.
We are a small shop, so would anyone target us?
Being targeted depends less on the size of the shop than on whether the platform's flaws remain open. In IPA's survey of 20 operators, 75% had not fixed known flaws. A small shop on the same platform has the same holes to find.
Frequently asked questions
What does an e-commerce assessment check?
We check login, the cart, the hand-off to payment, member screens and the admin screen, plus the state of the CMS core and its extensions. Tools scan broadly, and a person walks through the purchase flow by hand. We do not publish attack procedures.
How much does it cost?
A CMS-based shop such as EC-CUBE or WooCommerce is from JPY 49,800 (excl. tax, up to 30 pages). A custom-built shop is assessed as a web application: Lite is from JPY 98,000 (excl. tax, up to 10 screens) and Standard is from JPY 198,000 (excl. tax) and adds a person's manual checks of the screens behind login, up to 20 screens.
Could the assessment stop my live shop or damage order data?
We keep the load low, and any method that could affect the shop runs only in a time window agreed beforehand. For real payments and stock updates, we agree before the assessment whether to exclude them or to work in a test environment.
Do we need an assessment if we never hold card data ourselves?
You may. Without card numbers on your side, the area around the payment screen can still be rewritten, and customer names and addresses can still leak. An assessment confirms what actually sits on your own site.
Can you fix the holes the assessment finds?
Yes. An individual vulnerability fix is from JPY 10,000 per item (excl. tax), quoted by content. One re-assessment after the fixes is free.
Next step
If you want to see how your shop looks today before ordering anything, use the free URL check. It reads only what any visitor can see from outside, runs no attacks, and cannot see behind login or inside the server.
If the platform or the scope is unclear, contact us by form, phone or online meeting. We sign the NDA, at no cost, before assessment work begins.
Written by Mio Kanzaki (AI security analyst). Supervised by 千葉圭介. Updated 19 November 2026.
Frequently asked questions
What does an e-commerce assessment check?
We check login, the cart, the hand-off to payment, member screens and the admin screen, plus the state of the CMS core and its extensions. Tools scan broadly, and a person walks through the purchase flow by hand. We do not publish attack procedures.
How much does it cost?
A CMS-based shop such as EC-CUBE or WooCommerce is from JPY 49,800 (excl. tax, up to 30 pages). A custom-built shop is assessed as a web application: Lite is from JPY 98,000 (excl. tax, up to 10 screens) and Standard is from JPY 198,000 (excl. tax) and adds a person's manual checks of the screens behind login, up to 20 screens.
Could the assessment stop my live shop or damage order data?
We keep the load low, and any method that could affect the shop runs only in a time window agreed beforehand. For real payments and stock updates, we agree before the assessment whether to exclude them or to work in a test environment.
Do we need an assessment if we never hold card data ourselves?
You may. Without card numbers on your side, the area around the payment screen can still be rewritten, and customer names and addresses can still leak. An assessment confirms what actually sits on your own site.
Can you fix the holes the assessment finds?
Yes. An individual vulnerability fix is from JPY 10,000 per item (excl. tax), quoted by content. One re-assessment after the fixes is free.