LA-Studio Element Kit for Elementor <= 1.6.1 - Authenticated (Contributor+) Local File Inclusion via 'progress_type' Widget Setting
The LA-Studio Element Kit for Elementor plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.6.1 via the get_type_template function. This makes it possible for authenticated attackers, with contributor-level access and above, 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. The wp_normalize_path function used in get_template only normalizes directory separators and does not resolve or reject path traversal sequences, while the extension check is trivially bypassed because the caller already appends the required extension to the traversal payload.
Quick answer
LA-Studio Element Kit for Elementor should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-1.6.1
Fixed versions
- 1.6.2
How to fix it
LA-Studio Element Kit for Elementor is affected by CVE-2026-15338, a authorization bypass issue in versions up to 1.6.1. Wordfence lists the official remediation as updating to version 1.6.2, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, Elementor/page-builder surfaces, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has LA-Studio Element Kit for Elementor installed, including production, staging, multisite, client, and WooCommerce environments.
- Confirm the installed LA-Studio Element Kit for Elementor version and compare it with the affected range from the Wordfence advisory.
- Update LA-Studio Element Kit for Elementor to version 1.6.2, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable LA-Studio Element Kit for Elementor or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review affected REST endpoints, AJAX actions, roles, capabilities, account changes, orders, bookings, payments, and admin actions for unauthorized activity.
- Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, security plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running LA-Studio Element Kit for Elementor version is version 1.6.2 or newer, and record the patched version in the remediation ticket.
- Verify unauthenticated or low-privilege users can no longer trigger the affected action, endpoint, account, payment, booking, or settings change.
- Review web server, WordPress, security plugin, WAF, database, and application logs for exploitation attempts before and after the fix.
- Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, or integration workflows to confirm expected behavior still works.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-15338?
LA-Studio Element Kit for Elementor versions listed as affected should be reviewed: *-1.6.1.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.