CVE-2026-0920
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe LA-Studio Element Kit for Elementor plugin for WordPress is vulnerable to Administrative User Creation in all versions up to, and including, 1.5.6.3. This is due to the 'ajax_register_handle' function not restricting what user roles a user can register with. This makes it possible for unauthenticated attackers to supply the 'lakit_bkrole' parameter during registration and gain administrator access to the site.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe LA-Studio Element Kit for Elementor WordPress plugin contains a user registration function ('ajax_register_handle') that fails to validate or restrict the 'lakit_bkrole' parameter, allowing unauthenticated attackers to specify 'administrator' as their role during registration and immediately gain full administrative access to the WordPress site.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify LA-Studio Element Kit for Elementor is installedNavigate to WordPress dashboard > Plugins and look for 'LA-Studio Element Kit for Elementor' in the installed plugins list. If not found, you are not affected.Affected if The plugin is installed in your WordPress environment
-
Check the installed plugin versionIn the Plugins list, find 'LA-Studio Element Kit for Elementor' and locate the version number displayed below the plugin name. Compare this version to the fixed version 1.5.6.4 - versions prior to 1.5.6.4 are affected.Affected if The installed version is lower than 1.5.6.4
-
Confirm user registration is enabledGo to WordPress dashboard > Settings > General and locate the 'Membership' setting. Check if 'Anyone can register' is enabled. Also check if the 'New User Default Role' is set to Administrator.Affected if User registration is enabled and allows Administrator role as the default or can be manipulated via the lakir_bkrole parameter
-
Audit existing administrator accountsGo to WordPress dashboard > Users and review all accounts with Administrator role. Look for unfamiliar accounts, accounts created recently that you did not create, or accounts with suspicious usernames. Check the 'Registered' column for unexpected creation dates.Affected if Unexpected administrator accounts exist that you did not create, or administrator accounts were created around the time the vulnerable plugin was active
You are affected if the LA-Studio Element Kit for Elementor plugin is installed with a version lower than 1.5.6.4 and user registration is enabled on your site.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to a version beyond 1.5.6.3 when available; alternatively disable the registration functionality or the entire plugin. Audit existing user accounts for unauthorized administrators and remove any suspicious accounts created without authorization.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0920 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0920 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data