b2c-security
Find and fix security problems in B2C Commerce code and site data with the b2c CLI. Covers cartridge JavaScript (SFRA, SiteGenesis, custom cartridges) and site import/export data (OCAPI settings, services.xml, preferences). Use when the user asks to check code or a site_template for security issues, asks whether a specific snippet is safe (a query or redirect built from request input, credentials in code, crypto choices), audits a storefront before launch, reviews OCAPI settings or service credentials before an import, sets up security scanning in CI, or fixes findings such as open redirects, object query injection, CSRF gaps, weak crypto, hardcoded credentials, insecure cookies, mass assignment, or the OCAPI demo client ID.
Pinned to revision 0fee2877807e, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.