CVE-2026-103367 json
ShopMagic <= 4.9.0 - Unauthenticated Local File Inclusion via 'billing.first_name' Parameter
published 26d ago modified 26d ago also EUVD-2026-100903
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
The ShopMagic – email automation for WordPress plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.9.0 via the 'billing_address.first_name' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. Exploitation requires a published recipe that processes the {{ customer.first_name }} placeholder — the plugin's built-in "New Order email with social media profile links" recipe satisfies this requirement out of the box, making the default configuration exploitable with no account, cookie, or nonce by simply submitting a guest checkout with the payload as the billing first name.
Is CVE-2026-103367 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 26d ago
Exploit prediction
1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- wpdesk ShopMagic – email automation for WordPress
Classification
- Weakness
-
- CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/56c9fe56-8b15-409f-815b-10ee93f5153a?source=cve
- plugins.trac.wordpress.org /browser/shopmagic-for-woocommerce/tags/4.9.0/vendor_prefixed/wpdesk/wp-view/src/Renderer/SimplePhpRenderer.ph
- plugins.trac.wordpress.org /browser/shopmagic-for-woocommerce/tags/4.9.0/src/Workflow/Placeholder/Builtin/Order/OrderProductsOrdered.php#
- plugins.trac.wordpress.org /browser/shopmagic-for-woocommerce/tags/4.9.0/src/Workflow/Placeholder/PlaceholderProcessor.php#L47
- plugins.trac.wordpress.org /browser/shopmagic-for-woocommerce/tags/4.9.0/src/Workflow/Placeholder/Builtin/Customer/CustomerFirstName.php#
- plugins.trac.wordpress.org /browser/shopmagic-for-woocommerce/tags/4.9.0/src/Customer/Guest/GuestFactory.php#L34
- plugins.trac.wordpress.org /browser/shopmagic-for-woocommerce/tags/4.9.1
Sources
- CVE List CVE-2026-103367
- NVD CVE-2026-103367
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.