CVE-2026-24947
Missing Authorization in LA-Studio Element Kit Allows Unauthorized Access
Publication date: 2026-02-03
Last updated on: 2026-02-03
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| la-studio | element_kit_for_elementor | to 1.5.6.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'To mitigate this vulnerability, immediately update the LA-Studio Element Kit for Elementor plugin to version 1.5.6.3 or later, where the issue has been fixed.'}, {'type': 'paragraph', 'content': "Additionally, consider using mitigation services such as Patchstack's auto-updates for vulnerable plugins to ensure timely patching."}] [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
CVE-2026-24947 is a Broken Access Control vulnerability that allows unauthenticated users to perform actions requiring higher privileges due to missing authorization checks.
Such unauthorized access could potentially lead to exposure or modification of sensitive data, which may impact compliance with standards and regulations like GDPR or HIPAA that require strict access controls and protection of personal or health information.
However, the vulnerability is classified as low severity with a CVSS score of 4.3 and is considered unlikely to be exploited, which might reduce the immediate compliance risk.
To mitigate any compliance impact, it is recommended to update the plugin to version 1.5.6.3 or later where the issue is resolved.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability affects versions of the LA-Studio Element Kit for Elementor plugin prior to 1.5.6.3. Detection primarily involves identifying if the vulnerable plugin version is installed on your WordPress site.'}, {'type': 'paragraph', 'content': 'To detect the vulnerability, you can check the installed plugin version by accessing your WordPress admin dashboard or by using command line tools to inspect the plugin files.'}, {'type': 'list_item', 'content': 'Use WP-CLI to check the plugin version: wp plugin list | grep lastudio-element-kit'}, {'type': 'list_item', 'content': "Manually inspect the plugin's readme or main plugin file for the version number."}, {'type': 'paragraph', 'content': 'Since the vulnerability involves missing authorization checks, network detection is difficult without specific exploit signatures. Monitoring for unusual unauthenticated requests attempting privileged actions related to the plugin could help, but no specific commands or signatures are provided.'}, {'type': 'paragraph', 'content': 'The recommended mitigation is to update the plugin to version 1.5.6.3 or later.'}] [1]
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-24947 is a Broken Access Control vulnerability found in the WordPress plugin "LA-Studio Element Kit for Elementor" versions prior to 1.5.6.3.'}, {'type': 'paragraph', 'content': 'The issue arises from missing authorization, authentication, or nonce token checks within certain functions of the plugin.'}, {'type': 'paragraph', 'content': 'This allows unauthenticated users to perform actions that normally require higher privileges.'}, {'type': 'paragraph', 'content': 'It falls under the OWASP Top 10 category A1: Broken Access Control.'}] [1]
How can this vulnerability impact me? :
Because the vulnerability allows unauthenticated users to perform privileged actions, it can lead to unauthorized changes or access within the affected WordPress site.
However, the CVSS severity score is 4.3, indicating a low severity impact and it is considered unlikely to be exploited.
Users of the plugin should update to version 1.5.6.3 or later to mitigate this risk.