Closed six exposed issues on a self-hosted cookware store before launch

Client
A Canadian cookware e-commerce retailer
Engagement
Pre-launch hardening + Security Snapshot
Timeline
5 days

The situation

A small retailer was about to launch a self-hosted store built on Node.js and SQLite, with no CDN or managed platform patching anything for them.

They wanted to know, before taking real orders, whether anything was exposed that a scanner or an attacker would find first.

What we found

  • High The domain had no SPF, DKIM or DMARC, so anyone could send email that looked like it came from the store.
  • High An admin login path was reachable from the public internet with no attempt limit.
  • Medium Security headers were missing, and TLS was left on a default configuration.
  • Medium A staging copy of the site was indexable and served the same code as production.

What we did

  • Set SPF, DKIM and DMARC (monitor-only first, with a path to enforcement) and confirmed mail still delivered.
  • Put the admin path behind an attempt limit and removed it from the public surface.
  • Added the standard security headers and a starter CSP, and brought TLS up to a clean A rating.
  • Took the staging copy off the public internet and blocked it from search engines.

Before and after

AreaBeforeAfter
Email spoofingDomain fully spoofableDMARC in place, path to reject
Security gradeFailing header scanA rating
Admin exposureOpen, unlimited attemptsRate-limited, off public surface

Result

The store launched with none of the issues a basic scan would have flagged on day one, and a clear baseline to monitor against afterwards.

Want the same for your site?

Start with a free scan of what's public, or ask about a Security Snapshot. You get the finding and the fix, written up the same way.

Opens your email app with this filled in.