# CMS and storefront playbook: the first 72 hours after a critical flaw

Playbook, sources read 19 Nov 2026

**The short answer.** Content and commerce platforms run public PHP code with writable folders, so one flaw gives a web shell and often payment data. This playbook covers WordPress CVE-2026-119977 (fixed in 7.1.4 and backports to 4.7.39) and Adobe Commerce CVE-2026-75650 (hotfix VULN-39341, not a release), hour by hour.

A CMS or storefront is a large body of PHP code that anonymous visitors reach by design, on a host where the web user can write files. Flaws are exploited by getting attacker text onto disk and getting the application to run it: a log or error report that stores a request, a predictable upgrade folder, a template engine that builds objects from visitor input. The attacker gains code execution as the web user, then the database credentials, the admin session store, the payment integration keys and, on a shop, the checkout page itself.

Two things make patching harder than it looks. The fix may not be a version number: Adobe's fix for CVE-2026-75650 is a composer hotfix applied to every 2.4 release, so a version read says nothing about whether you are safe. And the upgrade can itself be the exposure: WordPress CVE-2026-119977 can be exploited only while a core upgrade is running, and the upgrade that installs the fix still runs the old, vulnerable updater.

## The steps, hour by hour

| Window | Owner | Step, and why it comes here | Record to keep |
| --- | --- | --- | --- |
| 0 to 1 hour | Security lead | Step 1. Inventory every WordPress install, including staging copies, agency-run sites and multisite networks, and read each version: wp core version, or grep wp_version wp-includes/version.php. WordPress CVE-2026-119977 affects 4.7.0 through 7.1.3. First fixed release per branch: 7.1.4, 7.0.8, 6.9.11, 6.8.12, 6.7.11, 6.6.11, 6.5.14, 6.4.14, 6.3.14, 6.2.15, 6.1.16, 6.0.18, 5.9.20, 5.8.19, 5.7.21, 5.6.23, 5.5.24, 5.4.25, 5.3.27, 5.2.30, 5.1.28, 5.0.31, 4.9.35, 4.8.34 and 4.7.39 (all released 28 Oct 2026; 7.1.5, 7.0.9 and 6.9.12 followed on 18 Nov 2026 and are the newest on their branches). Any site older than the backport for its branch, or on a branch below 4.7, is outside the vendor's fix.<br>The fixed version differs by branch, so a single 'update to latest' instruction fits only sites you control. | Site, branch, exact version, who updates it, whether automatic core updates are on. |
| 0 to 1 hour | Security lead | Step 2. Inventory Adobe Commerce, Adobe Commerce B2B and Magento Open Source stores. Read bin/magento --version, and for the hotfix run vendor/bin/magento-patches -n status \| grep "39341\\|Status" from the Magento root; the line for 39341 must show Applied. Affected: Adobe Commerce, Magento Open Source and Commerce B2B 1.3.3 to 1.5.3, on 2.4.4 to 2.4.9 at every patch level through the 2026-aug releases (Sansec: "Every version from 2.4.4 up to and including 2.4.9 is affected"; Adobe tested the hotfix on exactly that range). Older versions are affected in practice too: the NVD record built from Adobe's data lists 2.4.6 to 2.4.9 and every earlier version, and the unsupported branches 2.2, 2.3 and 2.4.0 to 2.4.3 get no Adobe patch. The fix is Adobe hotfix VULN-39341 from APSB26-146, a composer patch, not a new release number.<br>The version cannot tell you the answer, because a store on 2.4.6-p15 with the July and August patches was the first victim Sansec saw. | Store, product line, patch-status line for 39341 (Applied or not), public yes or no. |
| 1 to 2 hours | Platform engineering | Step 3. Block web access to the WordPress staging folder before any upgrade runs, including automatic ones. nginx: location ^~ /wp-content/upgrade/ { deny all; } . Apache: a Require all denied rule for the wp-content/upgrade directory. Reload the web server, then from outside run curl -sI https://your-site.example/wp-content/upgrade/ and expect 403 or 404. This rule comes from comparing the 7.1.3 and 7.1.4 code, not from a vendor statement; 7.1.4 itself adds an index.php to the folder and a 16 character random suffix to the working folder.<br>The upgrade that installs the fix still creates the predictable folder, so the block has to exist first. | Server config file and line, the curl status code before and after. |
| 1 to 2 hours | Platform engineering | Step 4. Put a WAF virtual patch on every Commerce and Magento store: Fastly offers one for its Next-Gen WAF and Sansec Shield blocks the variants it has seen. Treat it as compensating only. Take a disk snapshot, and copy var/log, var/report, a listing of pub/media and the cron spool file before the hotfix.<br>Exploitation began 4 Sep 2026, three days before the hotfix existed, and the vendors say payloads changed several times a day, so the WAF buys time and the evidence copy keeps the proof. | WAF rule id and time active; snapshot id; where the copies are stored. |
| 2 to 4 hours | Security lead | Step 5. Hunt a Commerce or Magento host for the indicators Sansec lists. Processes and cron: crontab -l \| grep -i gvfsd; ps -eo pid,comm,args \| grep -iE 'kworker\|fc-cache\|chronyd' (a chronyd or fc-cache process whose parent is PID 1 is suspect; also read the cron spool file, since an empty crontab is not proof). Files: grep -r 'crontab command not allowed' /var/log/ ; grep -ril 'x_trace_' var/report/ ; find -L pub/media -type f -name '*.php' (a sync_<10 hex>.php under pub/media/catalog/product/cache/ss_<10 hex>/ is a web shell, and a modified vendor/magento/framework/App/View.php that loads remote code is another sign). Network: C2 99[.]84[.]67[.]186 on 443, NTP-shaped beacons to ntp[.]timesync[.]to and ntp[.]timesysnc[.]net, download host 209[.]141[.]43[.]95, second C2 213[.]111[.]146[.]27.<br>Attackers were in stores before the hotfix, so patching alone leaves an existing web shell running. | Each hit with path, owner, modification time; any process with its parent PID. |
| 4 to 24 hours | Platform engineering | Step 6. Apply Adobe hotfix VULN-39341: download VULN-39341-composer-patches.zip from repo.magento.com, apply it as a composer patch on staging, deploy (static content and cache steps mean downtime), then re-run the vendor/bin/magento-patches status line and expect Applied. Stores on 2.2, 2.3 or 2.4.0 to 2.4.3 get no Adobe patch: upgrade to a supported release, or test Scandiweb's third-party backports (41 older releases, 2.2.0 to 2.4.3-p3) on a staging copy first, because Sansec states it has made no review of them.<br>Everything before this step only reduced exposure; the hotfix removes the flaw. | Time deployed per store, the status line, the output of the first working checkout test. |
| 4 to 24 hours | Platform engineering | Step 7. Update each WordPress site to the fixed release for its branch, for example wp core update --minor, and let automatic updates run once the staging block from step 3 is in place. After the upgrade, run wp core verify-checksums, wp user list --role=administrator and compare with the list you hold, ls -la wp-content/upgrade/ for leftover folders named after the package (wordpress-<version> with no random suffix), and a wp-config.php or any .php file in that folder. List new files under wp-content/uploads and wp-content/plugins. Search the web server log for requests to /wp-content/upgrade/ in the minutes around each past upgrade.<br>WordPress.org names no indicators, so file and account differences from a known-good state are the only evidence there is. | Version before and after, checksum result, administrator list, any leftover folder. |
| 24 to 72 hours | Platform engineering | Step 8. On every Commerce and Magento store, rotate what the attacker could read, as Adobe recommends: the encryption key and every credential it protected (admin passwords, REST, SOAP and GraphQL integration tokens, OAuth client secrets, payment gateway API credentials, database credentials, SSH and deploy keys, third-party extension API keys). Rotate at the source, not only in Magento, because changing the encryption key does not invalidate what was already read. Do it after the hotfix and the host hunt, so the new secrets are not handed to a shell that is still there.<br>Secrets read before the patch stay valid after it. | Each credential, where it was rotated, time, and who confirmed it works. |
| 24 to 72 hours | Application owner | Step 9. Test checkout, login, search, plugin and payment email flows on the fixed versions, and turn automatic core updates back on for WordPress if you turned them off. Check the mail log for bursts of the 'Payment Transaction Failed Reminder' email, which the exploit triggers, remembering that real declines send the same message.<br>Fixes on a shop break checkout in ways staging does not show, and the email burst is the only traffic-level sign of the attack. | Test cases passed, the declined-payment email count per day for the exposure window. |
| 24 to 72 hours | Communications | Step 10. If a web shell or modified file was found on a store that serves checkout, tell your payment processor or acquirer and your counsel the same day and agree on the customer notice. Name the window from the earliest file time, not from the patch date.<br>Processors usually require prompt notice of a suspected compromise on a card-handling host, and the earliest file time sets how many customers are in scope. | Date the host was first suspect, systems in scope, the notice sent. |

Print this table as the checklist: write the time each step was done in the record column.

## When no fix exists yet

For Adobe Commerce, the period before the hotfix was a no-fix case: exploitation from 4 Sep, hotfix on 7 Sep. The only mitigations were a WAF virtual patch, host monitoring and evidence collection. The WAF costs false positives on admin template edits. Moving sessions to Redis or the database does not stop the attack, and switching off outbound mail does not either, since the attack works when mail delivery fails. Unsupported branches still have no Adobe patch, so a third-party backport or an upgrade is the only route.

For WordPress the mitigation is the staging block plus restricting who and what can start an upgrade. It costs nothing for visitors. Take a store offline when indicators are found on a checkout host, or when the hotfix cannot be applied and the store runs an unsupported branch, because CISA's KEV action says to stop using the product if mitigations are unavailable. A maintenance page for a day costs less than a shell on the payment page.

## CVE-2026-75650 and CVE-2026-119977 worked through, hour by hour and then day by day

Adobe Commerce and Magento CVE-2026-75650 is a server-side template injection rated CVSS 10.0, exploited before Adobe's hotfix existed; its rows are timed in UTC hours. WordPress CVE-2026-119977 is an upgrade-window flaw rated CVSS 8.1 with a fix on the day of disclosure and a KEV listing six days later; its rows are given by day.

| When | What happened | Source |
| --- | --- | --- |
| 4 Sep 2026, 22:20 UTC | Sansec records the first confirmed exploitation of what it names StyleSmuggler. At 23:10 its scanner flags the implant on unrelated stores. The first victim ran 2.4.6-p15 with the July and August 2026 patches. | [source](https://sansec.io/research/stylesmuggler-0day) |
| 5 Sep 2026, 07:15 UTC | Sansec Shield starts blocking the attacks, and Sansec publishes the analysis the same day. | [source](https://sansec.io/research/stylesmuggler-0day) |
| 7 Sep 2026, 20:20 UTC | Adobe publishes APSB26-146 at priority 1 with hotfix VULN-39341 (time per Sansec). It ships as a composer patch, not a release. The bulletin's data appears in the NVD record below. | [source](https://sansec.io/research/stylesmuggler-0day) |
| 7 Sep 2026, 21:17 UTC | NVD publishes the record from Adobe's CNA data: CVSS 3.1 10.0, CWE-1336. | [source](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-75650) |
| 8 Sep 2026 | CISA adds the CVE to KEV, forensic triage required, due date 11 Sep 2026. SSVC: exploitation active, automatable yes, technical impact total. | [source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-75650) |
| 14 Sep 2026, 17:00 UTC | Sansec updates the article with further indicators. | [source](https://sansec.io/research/stylesmuggler-0day) |
| 16 Sep 2026 | Fastly publishes its analysis, a Nuclei template and a virtual patch, and says operators changed payloads several times a day. | [source](https://www.fastly.com/blog/what-is-style-smuggler-cve-2026-75650) |
| 28 Oct 2026 | WordPress 7.1.4 is released with fixes for the upgrade-process flaw (reported by Umut Bayram). Backports to every branch back to 4.7 (7.0.8 down to 4.7.39) ship the same day. | [source](https://wordpress.org/news/2026/10/wordpress-7-1-4) |
| 31 Oct 2026, 06:16 UTC | NVD publishes CVE-2026-119977 from the Wordfence CNA record: CVSS 3.1 8.1, attack complexity High, CWE-367. | [source](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-119977) |
| 3 Nov 2026 | CISA adds CVE-2026-119977 to KEV with a due date of 6 Nov 2026 and forensic triage Yes. This listing is the earliest dated public report of exploitation; CISA names no first exploitation date, actor or indicators, and WordPress.org lists none. | [source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-119977) |
| 18 Nov 2026 | WordPress 7.1.5, 7.0.9 and 6.9.12 are released as the newest builds on their branches. | [source](https://wordpress.org/download/releases/) |

From the first confirmed exploitation at 22:20 on 4 Sep to Adobe's hotfix at 20:20 on 7 Sep is 70 hours with no vendor fix. An owner who started on Sansec's article on 5 Sep would have read the patch status (step 2), put a WAF rule and an evidence copy in place (step 4) and run the host hunt (step 5) inside the first four hours, roughly two and a half days before the hotfix. Applied within 24 hours of its publication at 20:20 UTC on 7 Sep, the hotfix was in by 20:20 UTC on 8 Sep, the day CISA added the entry to KEV, and credential rotation fits before the 11 Sep due date, three days after listing. The step-2 patch-status line is the one that would have caught the patched-version trap: the 2.4.6-p15 store looked current and was not safe.

The WordPress flaw runs the other way: the fix existed on day 0 (28 Oct) and the KEV listing came on day 6 (3 Nov), with the due date on day 9 (6 Nov). A team that ran the inventory and the staging block (steps 1 and 3) inside the first two hours of 28 Oct and updated within 24 hours had a fixed fleet five days before the listing. A site left on its old version, or one that let an automatic update run without the block, was exposed for those six days.

## Related pages

- [The Windows operating system playbook for the first 72 hours](/playbooks/windows-endpoint-os/)
- [The artifact repository and CI system playbook for the first 72 hours](/playbooks/artifact-repository/)
- [The Linux server and SSH playbook for the first 72 hours](/playbooks/linux-server-ssh/)

## Sources

- WordPress 7.1.4 release note: https://wordpress.org/news/2026/10/wordpress-7-1-4 (read 19 Nov 2026)
- WordPress.org releases page: https://wordpress.org/download/releases/ (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-119977: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-119977 (read 19 Nov 2026)
- NVD record for CVE-2026-119977: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-119977 (read 19 Nov 2026)
- WordPress core class-wp-upgrader.php, 7.1.4 tag: https://raw.githubusercontent.com/WordPress/wordpress-develop/7.1.4/src/wp-admin/includes/class-wp-upgrader.php (read 19 Nov 2026)
- Sansec: StyleSmuggler, CVE-2026-75650: https://sansec.io/research/stylesmuggler-0day (read 19 Nov 2026)
- Fastly: Style Smuggler, CVE-2026-75650: https://www.fastly.com/blog/what-is-style-smuggler-cve-2026-75650 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-75650: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-75650 (read 19 Nov 2026)
- NVD record for CVE-2026-75650, carrying Adobe's APSB26-146 data: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-75650 (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://zerodayplaybook.com/playbooks/cms-and-storefront/
