Magento Penetration Testing
Magento penetration testing for the platform card skimmers know best. An integration saved with Resource Access set to All has a token that lasts until revoked, so one leak keeps working. CREST-certified testers, fixed price from £2,760 for a 2-day single-platform scope, quoted within 24 hours.
- Unlimited retesting
- No rescheduling or cancellation fees
- Fixed quote within 24 hours
“I would highly recommend EJN Labs to any organisation seeking reliable, detailed, and well-managed penetration testing services, particularly for government or enterprise-level projects.”
“There wasn’t another company we could find that could deliver what we needed in the timeframe we needed. The client loved it, and we got instant ROI from the engagement.”
Magento estates are large, extension-heavy and often behind on patches, which is why they have been the most reliably targeted commerce platform for years. The attack that matters is not defacement. It is a script on the payment page collecting card details while everything looks normal.
On a Magento store, the money is in the checkout and so is the risk
The failure modes are specific and repeatable. Admin left at the obvious path. Developer mode still set in env.php on the live server. Integrations saved with Resource Access set to All. Allow Anonymous Guest Access switched to Yes. The 2FA module disabled to get an integration working.
Integration tokens default to no expiry and last until someone revokes them, while admin tokens last 4 hours and customer tokens 1 hour. Setting oauth/consumer/enable_integration_as_bearer to 1 lets an integration token work on its own as a bearer token, so one leaked token keeps working until someone revokes it.
We test as a guest, a customer and the lowest admin role. We post a changed price into a guest cart, replay a coupon, call the REST and GraphQL APIs with a token issued for something else, and try to reach the admin and setup paths from outside. ISO 27001, SOC 2, PCI DSS and Cyber Essentials Plus audits accept manual penetration test evidence. Scan-only evidence is generally insufficient.
MAGENTO SPECIFICS
What We Actually Test in a Magento Store
Ten areas that apply because the store runs on Magento or Adobe Commerce, on top of the standard application checks. Every finding is verified, reproducible and mapped to OWASP, CWE, PCI DSS and CVSS 3.1.
Version and patch posture
The Magento or Adobe Commerce version deployed, applied security patches, and the issues that still apply.
Admin exposure
Admin path, brute force protection, two factor, session handling and account lockout.
Extensions
Installed extensions, abandoned ones, known flaws and anything reachable without authentication.
Template and layout handling
Layout XML, template injection paths and anything that renders administrator-controlled content.
Front end injection routes
Every path by which JavaScript can reach the checkout page, including third party tags and content delivery rules.
Checkout and pricing logic
Cart manipulation, price and quantity tampering, coupon and gift card stacking, and totals recalculation.
APIs
REST and GraphQL endpoints, customer data access, token handling and integration accounts.
Customer accounts
Registration, password reset, order history access and object level authorisation on customer data.
Infrastructure and configuration
File permissions, environment configuration, cron and indexer exposure, backups and media handling.
PCI boundary
Where cardholder data actually flows, what the integration method means for scope, and the evidence an assessor will want.
METHODOLOGY
What a Magento finding looks like
Written the way a finding appears in our reports. The example below is reconstructed from publicly documented research, with hosts, paths and identifiers redacted. We do not republish client findings, named or anonymised.
Template evaluation on a checkout field gives unauthenticated remote code execution
- Affected
- The guest checkout flow on [redacted], Adobe Commerce running two security patch levels behind.
- What we found
- A crafted value in an order field reached the template engine and was evaluated during order email generation. No account and no completed purchase was needed to reach the vulnerable path.
- Why it matters
- Remote code execution on the storefront. Card data was handled by hosted fields, but the platform still held full order history, addresses and customer accounts.
- Fix
- Apply the vendor patch, remove write permissions from the web user on the generated and static directories, add filtering at the edge for the known payload shapes, and review the site for existing web shells before treating the finding as closed.
Reconstructed from public research: CVE-2022-24086, improper input validation in Adobe Commerce and Magento Open Source, CVSS 3.1 base score 9.8.
Magento Penetration Testing: From Scope to Attestation
CREST-aligned methodology built on OWASP Web Security Testing Guide, OWASP ASVS, NIST SP 800-115, and PTES. Each finding maps to all four standards plus your specific compliance regime.
Reconnaissance
Application mapping, technology fingerprinting, content discovery, parameter enumeration, authentication-flow analysis, role-matrix construction.
Vulnerability Assessment
Authenticated and unauthenticated automated scanning across every user role, plus targeted manual checks for known weakness patterns.
Manual Exploitation
Hands-on testing by a CREST-certified pentester. Business-logic exploitation, chained vulnerabilities, privilege escalation, impact validation.
Reporting + Retest
Executive summary, technical report with CVSS scores and reproduction steps, walkthrough call, free retest after remediation, attestation letter.
CREDENTIALS
Verified Accreditations Auditors Accept
Every credential below is independently verifiable. UK procurement teams, FCA supervisors, ISO 27001 / SOC 2 auditors, and cyber insurance underwriters all recognise these standards.
GET YOUR QUOTE
Get a CREST Magento assessment pen test quote in 24 hours
A fixed-price quote back in one business day, from a named CREST assessor. No sales pipeline, no chasing.
- CREST and IASME accredited. Testing your auditors and clients already recognise.
- Fast-track testing within 24 hours where required. Free retest of every fix included.
- Live findings via your client portal, not a four-week PDF.
- Fixed price from £2,760 for a small, single-scope engagement, agreed up front. Most engagements run £4,180 and up. No day-rate surprises.
Dan WilcocksonFounder, CelloriUnder NDA Further named references available on a scoping call.
- We reply within one business day with a fixed-price quote from a named CREST assessor.
- You approve the scope and we book a start date, usually within 24 hours.
- Live findings land in your client portal as we test, with a free retest of every fix.
Get your fixed pen test quote in 24 hours
Quote request received
We will reply within one business day with your fixed-price quote from a named CREST assessor.
Your data stays with us. No newsletter signup.
or book a 20-min scoping call first
We reply within one business day. Your data stays with us. No newsletter signup.
COMPLIANCE READY
Reports Mapped to Every Framework
Findings are explicitly tagged to the relevant control reference. Your audit team submits the report directly without translation work.
ISO 27001:2022
Annex A.8.8 management of technical vulnerabilities plus A.5.15-5.18 and A.8.2-8.5 access control validation.
SOC 2 Type I & II
CC6 logical access, CC7 system operations, CC8 change management evidence.
PCI DSS
Requirement 11.4 application penetration testing across cardholder data environments, including ecommerce penetration testing for online retail platforms.
FCA SYSC
SYSC 4.1.1R, 6.1.1R, 13 mapped to each finding for FCA-regulated firms.
UK GDPR
Article 32 effectiveness testing, customer-data security controls, ICO-acceptable evidence.
Cyber Essentials Plus
Direct certification through our IASME body status, single-vendor delivery.
PRICING
Transparent Magento Penetration Testing Pricing
Pricing depends on app complexity, user-role count, business-logic depth, and integration surface. The day count flexes; the included deliverables stay the same across all engagements.
2 to 4 testing days
Single user role, basic CRUD application, marketing website with auth. Around 5 working days from kickoff to report.
Get a fixed quote4 to 5 testing days
Multi-role SaaS, business application with payment integration. Around 8 to 12 working days from kickoff to report.
Get a fixed quote5 to 7 testing days
Multi-tenant platform, complex authorisation matrix, integration-heavy applications. Around 15 to 20 working days from kickoff to report.
Get a fixed quotePart of Technologies We Pen Test. These are examples of the stacks we publish pages for, not a complete list. If yours is not here we still test it. Related pages:
BY SECTOR
Magento Penetration Testing for Your Sector
Sector-specialist scoping for UK businesses with sector-specific compliance regimes and threat models.
Fintech & FCA-Regulated
FCA SYSC, Open Banking FAPI 1.0, PSD2 SCA, payment-flow scrutiny, KYC/AML testing.
Fintech sector pageSaaS Companies
SOC 2 Type I & II evidence, multi-tenant boundaries, role escalation, customer-tenant isolation.
SaaS sector pageLaw Firms
SRA Cyber Standard, privileged data, conveyancing fraud defence, partner-tier procurement.
Law firm sector pageHealthcare
NHS DTAC, DSP Toolkit v6, UK GDPR Article 32, EHR systems, telehealth platforms.
Healthcare sector pageInsurance
FCA / PRA Operational Resilience, cyber underwriting, claims data, broker portals.
Insurance sector pagePublic Sector
CCS / G-Cloud framework, NCSC-aligned, citizen-facing services, PSN-compliance scrutiny.
Public sector pageWHY EJN LABS
What You Get From Magento Penetration Testing
Six concrete differentiators competitors don’t all match.
CREST-Certified Testers, Verifiable
Every test by a CREST-certified pen tester (CRT, CCT APP, CCT INF where applicable). Verify our company status at crest-approved.org.
24-Hour Startup, Where Required
From signed scope to active testing in a single business day for incident response, audit deadlines, or regulator-driven timelines.
Live Findings, Not 4-Week PDFs
Critical issues reported during testing through your client portal. Your team remediates while testing continues.
Audit-Ready Reports
Executive summary plus full technical report with CVSS scores and explicit framework mappings (ISO 27001, SOC 2, PCI DSS, FCA SYSC).
Free Retests, Standard
Verify remediation of every finding before close-out. Letter of attestation for audit submission included. Most competitors charge £1,500-£3,000 per retest.
UK-Based CREST Testers
Every engagement performed by vetted, UK-based CREST-certified testers, matched to your needs, security clearance, and compliance scope.
FAQ
Frequently Asked
Do you test Magento 1 estates?
Yes. Magento 1 is unsupported, so expect findings that only a migration fixes, and we will say so plainly.
Will you test in production?
We prefer a staging copy with realistic data. Where production is unavoidable we agree strict limits, especially around orders.
Can you test our payment integration?
We test the boundary and the flow. We never transact with real cards and we use the provider test mode.
Our store is still in developer mode. Is that a problem?
On a live store, yes. In developer mode uncaught exceptions display in the browser, logging in var/report is verbose and the custom X-Magento headers are shown, whereas production mode logs errors to files and never displays them. Mode is stored in env.php, so we check what the live server is actually set to and what an error page gives away. See Adobe’s application modes page.
What about Adobe Commerce Cloud?
Covered, including the cloud configuration that sits around the application.
Do you check for existing skimmers?
We look for injected scripts as part of the test, but this is a penetration test rather than a forensic investigation.
What exactly do you test on a Magento store?
Your store: custom and third-party extensions, admin roles, the GraphQL and REST APIs, the storefront and checkout, and the hosting configuration around it. Adobe’s own infrastructure is not in scope. See our retail and e-commerce and checkout and payment flow testing pages.
Our admin is still at the default path. Does that matter?
Adobe recommends a custom Admin URL rather than the obvious Admin or Backend path, but a hidden path is not a control by itself. We test what sits behind it: login lockout, session handling, the 2FA enrolment step and whether any admin role can reach more than it should.
We saved an integration with Resource Access set to All. Is that safe?
Magento lets you choose All or Custom for each integration, and with Custom you tick each resource that is needed. The integration token has no expiry until it is revoked. We test what the token can read and change, and what a Custom scope would have blocked. Integration setup is covered in Adobe’s integrations guide.
We disabled the 2FA module to get an integration working. Is that safe?
Since 2.4.0 two-factor authentication is on by default for the Admin and required before an admin can log in through the UI or a web API, and Adobe strongly recommends against disabling the module. With it off, an admin password alone opens the Admin. We test whether that is the case on your store and what an admin session can do.
20+ CREST-accredited testing services in one place
Web, mobile, API, cloud, AI, infrastructure, red team. Pick the test that fits your environment.
Get your Magento store tested properly
Send us the store and a staging copy if you have one. You will have a fixed scope and a number within 24 hours.
