Skip to content
Knowledge base Updated: February 5, 2026

E-Commerce Pentests: Specific Threats and Penetration Testing Requirements for Online Stores

Online stores combine payment data, personal information, and financial transactions - an ideal combination for cybercriminals. Learn how professional pentests help secure e-commerce platforms.

E-commerce platforms are among the most attractive targets for cybercriminals. They combine everything attackers are looking for: credit card data, customer personal data, opportunities for financial fraud, and often weak security resulting from time-to-market pressure.

This article describes the specifics of penetration testing for electronic commerce platforms.

Why E-commerce is a Special Target

Valuable Data

Payment data:

  • Credit card numbers
  • CVV/CVC
  • Payment data for various providers
  • Payment tokens

Personal data:

  • Names, addresses
  • Phone numbers, emails
  • Purchase history
  • Shopping preferences

Business data:

  • Prices and margins
  • Supplier data
  • Pricing strategies
  • Sales data

Fraud Opportunities

  • Fraud using stolen cards
  • Price manipulation
  • Return fraud
  • Loyalty program theft
  • Gift card fraud

Typical Weaknesses

  • Pressure for quick deployments (time-to-market)
  • Many integrations with external systems
  • Seasonal load peaks
  • Frequent code changes (promotions, sales)

📚 Read the complete guide: OT/ICS Security: Bezpieczeństwo systemów OT/ICS - różnice z IT, zagrożenia, praktyki

Key Testing Areas

1. Payment Process

What to test:

a) Price manipulation

  • Can price be modified in request?
  • Is price validation server-side?
  • Is price verified before payment finalization?

b) Quantity manipulation

  • Negative product quantities
  • Fractional quantities
  • Exceeding inventory levels

c) Promotional codes

  • Multiple use of one-time codes
  • Discount stacking
  • Discount value manipulation
  • Race conditions when using codes

d) Payments

  • Can payment step be skipped?
  • Is callback from gateway validated?
  • Are payment tokens secure?

2. User Account Management

a) Registration

  • Email validation (can you register on others’ addresses?)
  • Password policy
  • Protection against mass registration
  • Account enumeration

b) Login

c) Password recovery

  • Token security (is link one-time, does it expire?)
  • Information disclosure (does system confirm account existence?)
  • Account takeover via reset

d) User profile

  • IDOR (access to others’ data)
  • Email change without verification
  • Delivery address editing

3. Cart and Checkout

a) Race conditions

  • Multiple placement of same order
  • Using promotion more than once
  • Inventory state change between steps

b) Business logic

  • Skipping checkout steps
  • Changing delivery method after price calculation
  • Adding products after discount applied

c) Gift cards and vouchers

  • Number predictability
  • Number brute force
  • Double spending

4. Admin Panel

a) Access

  • Panel exposure (is it publicly accessible?)
  • Weak credentials
  • Missing MFA

b) Permissions

  • Privilege escalation
  • Access to functions outside role
  • Customer data export

c) Critical functions

  • Price changes
  • Creating discount codes
  • Access to payment data
  • Order modification

5. External Integrations

a) Payment gateways

  • Callback/webhook security
  • Signature validation
  • Replay attack resistance

b) ERP/CRM systems

  • API security
  • Data synchronization
  • Credential management

c) Logistics providers

  • API for labels and tracking
  • Access to address data

d) Marketing and analytics

  • Pixel tracking
  • Data leakage through third-party scripts

6. Search and Catalog

a) SQL Injection

  • Search parameters
  • Category filters
  • Sorting

b) XSS

  • Search results
  • Product descriptions
  • User reviews

c) Information disclosure

  • Wholesale prices in response
  • Inventory data
  • Supplier information

7. Mobile App (if exists)

a) API security

  • Authentication
  • Certificate pinning bypass
  • Sensitive data in local storage

b) Business logic

  • Consistency with web version
  • Mobile-specific vulnerabilities

Compliance and Regulations

PCI DSS

If you process card data:

Pentest requirements (11.3):

  • Penetration tests at least annually
  • After significant infrastructure changes
  • External and internal tests
  • Application layer tests

Scope:

  • Cardholder Data Environment (CDE)
  • Systems connected to CDE
  • Segmentation testing

GDPR

Key areas:

Consumer Law

  • Fraud protection
  • Price accuracy
  • Terms and policies

Typical E-commerce Vulnerabilities

TOP 10 Findings

  1. IDOR in orders – access to other users’ orders
  2. Price manipulation – changing price in request
  3. Coupon abuse – multiple code usage
  4. Weak password reset – predictable tokens
  5. Missing rate limiting – brute force on login/codes
  6. XSS in reviews – user-generated content without sanitization
  7. SQL Injection in search – product filters
  8. Insecure direct object reference – access to profiles/addresses
  9. Business logic flaws – skipping payment, free shipping
  10. Admin panel exposure – /admin without protection

Real Scenario Examples

Scenario 1: Free Shopping

  1. Add product to cart
  2. Proceed to payment
  3. Intercept request with price
  4. Change value to 0.01
  5. Finalize order

Scenario 2: Gift Card Brute Force

  1. Identify gift card number format (16 digits)
  2. Discover pattern (fixed prefix, sequential rest)
  3. Brute force active numbers
  4. Use on own account

Scenario 3: Coupon Race Condition

  1. One-time discount code for -50%
  2. Open two browser windows
  3. Add same code in both simultaneously
  4. Both orders receive discount

E-commerce Testing Methodology

Phase 1: Reconnaissance

  • Platform identification (Magento, WooCommerce, PrestaShop, custom)
  • Functionality mapping
  • Integration identification
  • Understanding purchase flow

Phase 2: Authentication & Authorization

  • Registration and login tests
  • Password policy
  • Session management
  • Access control

Phase 3: Business Logic

  • Price and quantity manipulation
  • Discount codes and promotions
  • Gift cards
  • Checkout flow

Phase 4: Technical Vulnerabilities

Phase 5: Integrations

  • Payment gateway security
  • Webhook validation
  • API security

Phase 6: Admin Panel

  • Access control
  • Privilege escalation
  • Critical function testing

Recommendations for E-commerce

Quick Wins

  1. Server-side validation of everything – prices, quantities, discounts
  2. Rate limiting – on login, password reset, promo codes
  3. Hide admin panel – non-standard URL, IP whitelist, VPN
  4. MFA for admins – mandatory
  5. Logging and monitoring – alerting on anomalies

Long-term

  1. Security by design – include security in development process
  2. Regular pentests – minimum annually, before season
  3. Bug bounty – for large platforms
  4. WAF – Web Application Firewall with e-commerce rules
  5. Fraud detection – fraud detection systems

Summary

E-commerce penetration testing requires:

  1. Business understanding – pentester must understand purchase flow
  2. Focus on business logic – not just technical CVEs
  3. Integration testing – payments, ERP, logistics
  4. Compliance consideration – PCI DSS, GDPR
  5. Seasonal approach – tests before Black Friday, holidays

E-commerce platform compromise isn’t just data leak – it’s loss of customer trust, regulatory penalties, and direct financial losses.


Running an e-commerce platform and want to examine its security? Contact us – we’ll conduct tests tailored to electronic commerce specifics.

Learn key terms related to this article in our cybersecurity glossary:


Learn More

Explore related articles in our knowledge base:


Explore Our Services

Need cybersecurity support? Check out:


Explore Our Products

Solutions mentioned in this article that can help protect your organization:

Cybersecurity for Your Industry

Learn more about cybersecurity in your industry:

Share:

Talk to an expert

Have questions about this topic? Get in touch with our specialist.

Sales Representative
Grzegorz Gnych

Grzegorz Gnych

Sales Representative

Response within 24 hours
Free consultation
Individual approach

Providing your phone number will speed up contact.

Want to Reduce IT Risk and Costs?

Book a free consultation - we respond within 24h

Response in 24h Free quote No obligations

Or download free guide:

Download NIS2 Checklist