🌐 Language: 🇻🇳 Tiếng Việt · 🇬🇧 English (current) · 🇯🇵 日本語
S-Cart releases and security
Introduction
This page is for S-Cart (3.x line) site owners and operators: it tells you what each release brings, which version to run and how to update. Latest release: S-Cart 3.10.0 (2026-11-20).
Recommended versions
Run php artisan gp247:info (or composer show "gp247/*") and compare each line with the Recommended minimum column:
| Package | Recommended minimum | Latest |
|---|---|---|
| gp247/core | 3.16.0 | 3.16.0 |
| gp247/front | 3.11.0 | 3.12.1 |
| gp247/shop | 3.12.0 | 3.13.1 |
| gp247/mcp | 2.0.1 | 2.1.1 |
- Below the "Recommended minimum" column → update when you can.
- At or above it → your site has all the important improvements, even if you have not reinstalled S-Cart.
- Third-party libraries → also run
composer audit; see Third-party libraries.
⚠️ Note: update all the packages together:
gp247/shop3.12.0 needsgp247/front≥ 3.11,gp247/front3.10.0 and later needgp247/core≥ 3.14.2,gp247/shop3.11.3 and later needgp247/core≥ 3.14.1,gp247/front3.9.1 andgp247/shop3.11.1 needgp247/core≥ 3.14,gp247/front3.8.1 andgp247/shop3.10.1 needgp247/core≥ 3.12.1,gp247/front3.7.0 andgp247/shop3.9.0 needgp247/core≥ 3.11,gp247/shop3.8.1 needsgp247/core≥ 3.10.3,gp247/mcp2.0.1 needsgp247/core≥ 3.9,gp247/shop3.6.0 needsgp247/core≥ 3.7,gp247/front3.2.3 needsgp247/core≥ 3.2.3. Which lines are still supported: see Support lifecycle.
Support lifecycle
| Line | Platform | Status | Security fixes until |
|---|---|---|---|
| 3.x | Laravel 13 · PHP 8.3+ | ✅ Supported | March 2028 |
| 2.x and earlier | Laravel 12–13 | ⛔ No longer supported | — |
- New features go into the newest line only.
- When a new line ships: the previous line gets critical bug fixes for 6 more months and security fixes until the time in the table — never past the security support of the Laravel version that line runs on.
- Sites still on 2.x or earlier: they keep running but receive no more fixes. 2.1 / 2.2 sites move to 3.x with
composer require … -Wandphp artisan gp247:update— see Upgrading to the 3.x line.
Highlights
- GA4, GTM and Meta Pixel tracking — paste the ID; the code runs only for the cookie groups the visitor allows (S-Cart 3.10)
- Cookie banner — ask first, notice only, or off (S-Cart 3.10)
- Ad revenue in GA4 and Meta — sales events are sent automatically (S-Cart 3.10)
- Duplicate products and pages — one button makes a copy; change only what differs (S-Cart 3.10)
How to update
Step 1 — Back up the database and the site folder.
Step 2 — Update the code:
composer update gp247/core gp247/front gp247/shop gp247/mcp
A site installed before S-Cart 3.5.0 has no MCP server yet: run composer require gp247/mcp -W once instead of the command above.
Step 3 — Apply data, configuration and cache updates:
php artisan gp247:update
Step 4 — Check the versions again with php artisan gp247:info.
A release may need extra steps — see its 📋 To do when updating below. Step-by-step details: Updating GP247 and S-Cart.
Releases
Newest first. An x.Y release brings new features; an x.y.Z release only fixes bugs.
S-Cart 3.10.0 — 2026-11-20
Add GA4 and Meta Pixel by pasting an ID, with a cookie banner; duplicate a product in one click.
✨ New
- GA4, GTM and Meta Pixel tracking — paste the ID; the code runs only for the cookie groups the visitor allows (docs)
- Cookie banner — ask first, notice only, or off; visitors change their mind any time through "Cookie settings"
- Ad revenue in GA4 and Meta — product view, add to cart, checkout and purchase events are sent automatically
- Security headers — switch each header on or off and turn HSTS on step by step from the admin (docs)
- Duplicate products and pages — one button makes a switched-off copy; change only what differs (docs)
- Find products by name in the admin product list; the category filter has a search box
- For developers: templates change the banner colours with CSS variables; import plugins write 301s from another platform's old addresses; plugins copy their own data when a product is duplicated (docs)
🔧 Improvements: saving products, customers and orders no longer reports duplicate keys on sites with a lot of data; 301 redirects also work for addresses that match no page (e.g. taken from the 404 log); category pages open faster on large stores
📋 To do when updating
- Run
composer update, thenphp artisan gp247:update(adds an index to the product–category table; on very large stores run it from the command line outside peak hours) - After the update the site sends four security headers; if the site must be embedded (iframe) on another domain, switch X-Frame-Options off on the Security headers screen
- Tracking code and the cookie banner are off by default — to use them, go to SEO › Tracking code & cookies (Administrators only)
- (Running with Docker) take the new
docker/nginx/default.conffrom S-Cart so headers are not sent twice; if you edited that file, merge the change - (Custom templates) keep
<x-gp247-front::meta-head>in<head>to get the tracking code and the cookie banner
Includes core 3.16.0 · front 3.12.0 · shop 3.13.0 · mcp 2.1.1 · GitHub Release
S-Cart 3.9.0 — 2026-11-18
Full SEO built in: an SEO tab for every product, automatic 301s when an address changes, an SEO check screen.
✨ New
- SEO tab for each piece of content — your own Google title and description, share image, noindex and canonical for products, categories, brands and pages (docs)
- Automatic 301 redirect when an address changes — old links from Google, Facebook and bookmarks still take visitors to the new page
- SEO check and 404 log screens — list what is To fix / To review with a link to fix it, with a reminder in System alerts; AI agents can read them through MCP (docs)
- Google/Bing verification, title templates, IndexNow right on the Meta & JSON-LD screen, with step-by-step help (docs)
- Private and filter pages hidden from Google automatically — plus automatic hreflang and richer product JSON-LD (docs)
- One Customize theme entry for every template — pick a template, then open its settings page
- For developers: plugins/templates plug into the SEO tab, sitemap, JSON-LD and system alerts;
gp247:doctoralso prints package checks (docs)
🔧 Improvements: sub-store admins can only save and delete pages, links, layout blocks, brands and categories of their own store (multi-store sites); a switched-off promotion no longer sets the selling price; the storefront shows 5 products per row on wide screens
📋 To do when updating
- Run
composer update, thenphp artisan gp247:update(creates the new SEO tables and menu) - Grant the two new screens SEO check and 404 log to admins who are not the main administrator
- (Your own template, or an overridden
meta-head) follow the template SEO contract so robots, hreflang and verification tags are printed - (Sites using the News plugin) update News to 3.1.0 or later to get the SEO tab for news
Includes core 3.15.0 · front 3.11.0 · shop 3.12.0 · mcp 2.1.0 · GitHub Release
S-Cart 3.8.0 — 2026-11-15
Shoppers sort products their way; the extension library shows everything and which core each needs.
✨ New
- Product sorting for shoppers — Featured, Newest, Best selling, Price low/high, Name A–Z; price sorting uses the running promotion price
- Tidier product filter bar — search and sort on one row, price range and brands on another, Enter applies the price
- Full online extension library — extensions that need a newer core say "Needs core X.Y+" instead of Install; group filters count across the whole library
- For developers:
gp247:shop-sampleuses the S-Cart photo set instead of random images
🔧 Improvements: og:image uses only the page image or the store's share image; extra allowed origins of the MCP server
work again; a fresh site no longer re-runs old upgrade migrations on its first gp247:update
📋 To do when updating
- Run
composer update, thenphp artisan gp247:update - The sample share image
org.jpgis gone: set your own under Website information if you want an image when links are shared - (Old links with
sort_asc/sort_desc) now show the default order set in the admin
Includes core 3.14.0 · front 3.9.1 · shop 3.11.1 · mcp 2.0.3 · GitHub Release
S-Cart 3.7.0 — 2026-11-13
Names and content show exactly as you type them — no more &.
✨ New
- Text stored as typed — product, category and page names with
&,<,"show correctly in the admin, the storefront and the API; existing data is converted during the update - Passwords and secrets keep every character — passwords with
& < > "sign in; SMTP passwords and payment keys reach the server unchanged - Raw HTML output warning — System alerts and
gp247:doctorpoint to the site's own templates and plugins that print a variable with{!! !!}(docs) - Untrusted proxy warning — alerts when admin pages come through a proxy missing from
TRUSTED_PROXIES, with the value to add (docs) - Server info shows GP247 versions first — compare with the "Recommended versions" table without the command line
- For developers:
gp247_text_plain()replacesgp247_clean()(deprecated, removed in 4.0), escape on output with{{ }}; the REST API returns text as typed; shared write services for products, categories, brands, suppliers and customers
🔧 Improvements: text entered by customers and admins always shows as text on the storefront and order screens; list
sorting accepts only valid columns; gp247:info prints versions as tagged (3.12.1, no longer 3.12.1.0)
📋 To do when updating
- Back up the database first —
gp247:updateconverts text stored HTML-encoded (&→&) once; this cannot be undone - Run
composer update, thenphp artisan gp247:update - Open System alerts (or
php artisan gp247:doctor): change{!! !!}prints of variables in your own templates and plugins to{{ }}, except HTML written in the rich-text editor - SMTP passwords or secret keys containing
& < > "saved before this release: enter them again once - (Apps using the REST API) strings now come back as typed (
&, not&) — the app must escape them when displaying
Includes core 3.12.1 · front 3.8.1 · shop 3.10.1 · mcp 2.0.2 · GitHub Release
S-Cart 3.6.1 — 2026-11-11
Backup and restore hardened for real sites and shared hosts — recommended update.
✨ New
- Each backup group says what it holds — the backup and restore screens show which data a group contains before you choose (docs)
- The restore preview says what is not brought back — columns the site no longer has need a separate confirmation; a backup newer than the site names the missing updates (docs)
- Warning when no full backup is available — the backup screen warns when there is no verified full backup, or it is old
🔧 Improvements: a restore left unfinished ends by itself and takes the site out of maintenance; backups handle large tables without a primary key and tables of wide rows within 128 MB, and retention always keeps the newest full backup; admin screens with file uploads no longer run out of memory
📋 To do when updating
- Run
composer update, thenphp artisan gp247:update - Verifying, unpinning and deleting backups, and saving backup settings, now ask you to confirm your sign-in; repeated wrong backup passwords are temporarily blocked
- (Restoring from the command line) a backup with columns the site no longer has: preview it, then run again with
--accept-column-loss
Includes core 3.11.2 · front 3.7.1 · shop 3.9.1 · mcp 2.0.2 · GitHub Release
Older releases
| Release | Date | Summary |
|---|---|---|
| S-Cart 3.6.0 | 2026-11-09 | Backup and restore built into S-Cart, ready for shared hosting |
| S-Cart 3.5.2 | 2026-11-07 | Improvements for sites on Docker or behind a proxy / CDN |
| S-Cart 3.5.1 | 2026-11-05 | The admin flags unsafe settings; a simpler web installer |
| S-Cart 3.5.0 | 2026-11-03 | Built-in MCP server: ask and manage your shop with an AI agent |
| S-Cart 3.4.0 | 2026-11-02 | Sell through your own app and sync with your ERP over the REST API |
| S-Cart 3.3.1 | 2026-10-29 | Contact form with an inbox; REST API switched on and off from the admin |
| S-Cart 3.2 | 2026-10-23 | Japanese, standard shipping with shipments, storefront theme that updates with the package |
| S-Cart 3.1 | 2026-10-03 | Payment requests outside the cart; stored passwords and payment keys encrypted |
| S-Cart 3.0.1 | 2026-09-04 | Old sc:* commands removed, use the gp247:* commands — command list |
| S-Cart 3.0 | 2026-08-30 | Start of the 3.x line: a payment ledger per order, discounts taken before tax — v3.0 notes |
Security
Keeping a site secure is more than updating — configuration, encryption keys, backups, accounts and incident response are covered in GP247 system security.
GP247 reviews security regularly, and improvements ship in every release. The simplest way to keep your site safe is to run at least the versions in Recommended versions and update when a new release comes out.
Server software (PHP, web server)
Flaws in PHP and the web server are fixed by their own vendors, not by a GP247 release — keep them up to date as well.
| Issue | Severity | Fixed in PHP |
|---|---|---|
| PHP2Shell — remote code execution (CVE-2026-109618, CVE-2026-109619) · 2026-10-21 | Critical | 8.3.36 · 8.4.27 · 8.5.12 |
What to do
- Check your PHP version:
php -v, or Admin → Server info. - PHP from the official releases (php.net, the official Docker images, most control panels that let you pick a version): move to the fixed version of your branch, or later.
- PHP managed by your Linux distribution (Ubuntu, Debian, RHEL…) or hosting provider: these vendors often patch an older version number, so the number alone does not tell you whether you are safe — install the latest operating system updates, or ask your provider whether CVE-2026-109618 and CVE-2026-109619 are patched.
- Cannot update yet: set
session.upload_progress.enabled = Offinphp.ini(GP247 does not use this feature) and restart PHP. It lowers the risk; it does not replace the update. - Running with Docker: follow "Security updates" in DOCKER.md.
Third-party libraries
Flaws in libraries GP247 uses (Livewire, Symfony…) are fixed by their own maintainers; GP247 raises its minimum when needed. GP247's own code does not use the affected features of the two flaws below, but third-party plugins may — update anyway.
| Issue | Severity | Fixed in |
|---|---|---|
| Livewire — authorization bypass (GHSA-mhf7-xp6r-6qrc) | Medium | livewire/livewire 4.4.8 (required by core 3.10.2) |
| symfony/mime — email header injection (CVE-2026-45070) | Medium | symfony/mime 7.4.22 |
What to do
- Update:
composer update, then check withcomposer show livewire/livewire symfony/mime. - Check every library at once:
composer auditlists the libraries on your site that have a published flaw.
Reporting a vulnerability
If you find a vulnerability, please email support@gp247.net — do not open a public GitHub issue, so the problem is not exposed before a fix is released.
📅 Last updated: 2026-11-22 · ✍️ Author: GP247