Nyla <= 1.7 - Unauthenticated Arbitrary Shortcode Execution
Strategic Overview
- Status
- Unpatched
- Affected Theme
- Nyla - A Fresh & Modern WooCommerce Theme
- Affected Version
<= 1.7- CVSS
- 6.5Medium
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2026-39642
At a glance
CVE-2026-39642 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Nyla - A Fresh & Modern WooCommerce Theme WordPress theme, affecting versions <= 1.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2026, reported by João Pedro Soares de Alcântara.
Vulnerability Overview
The The Nyla - A Fresh & Modern WooCommerce Theme theme for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.7. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Nyla - A Fresh & Modern WooCommerce Theme <= 1.7 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. No fixed build of this theme is recorded for Nyla - A Fresh & Modern WooCommerce Theme yet, so installs running <= 1.7 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Scanner
- Login Security
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C