How to fix info disclosure x powered by on BigCommerce

Steps for BigCommerce

1. BigCommerce is a fully managed SaaS platform; core HTTP response headers are controlled by BigCommerce's infrastructure and cannot be changed from the merchant admin.
2. If X-Powered-By is flagged on a BigCommerce storefront, raise a support ticket with BigCommerce to request header suppression, or note it as a platform-level finding outside merchant control.
3. If you use a custom headless front-end (e.g., Next.js via BigCommerce's headless channel), remove the header there: in next.config.js add a `headers()` async function returning `{ source: '/(.*)', headers: [{ key: 'X-Powered-By', value: '' }] }` and set `poweredByHeader: false`.

# Nginx — strip X-Powered-By in server block
more_clear_headers 'X-Powered-By';

# Apache .htaccess — unset header
Header unset X-Powered-By

# PHP — suppress PHP version header
expose_php = Off          # php.ini
header_remove('X-Powered-By');  # PHP code

# Next.js — next.config.js
module.exports = {
  poweredByHeader: false,
};

What is info disclosure x powered by?

Every time someone visits your store, your web server sends back a set of "headers" — invisible metadata that browsers and tools can read. One of these, X-Powered-By, often announces exactly what software is running your site (e.g., "WP Engine", "PHP/8.1", "Express"). This header serves no useful purpose for your customers but acts like a neon sign telling attackers which known vulnerabilities to target. Removing or masking it is a simple hardening step that reduces your visible attack surface.

Attackers routinely scan millions of sites for this header and then cross-reference the disclosed technology with published CVE vulnerability databases — meaning an exposed X-Powered-By header can make your store a faster, easier target for automated exploits. While removing it doesn't fix underlying vulnerabilities, it raises the effort required to fingerprint your stack and is a baseline expectation in security audits and PCI-DSS compliance reviews. Failing this check can flag your store in penetration tests, risk assessments, and payment-processor security questionnaires, potentially affecting your ability to process cards. It is specifically called out under OWASP A05:2021 – Security Misconfiguration as an information-disclosure risk.

See the complete Info disclosure x powered by guide for every platform and the full background.