dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4362

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The ElementsKit Elementor Addons plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `Live_Action::reset()` function in all versions up to, and including, 3.8.2 The function is hooked to the WordPress `init` action and triggers when both `post` and `action=elementor` GET parameters are present, with no authentication or nonce verification. This makes it possible for unauthenticated attackers to overwrite the Elementor content (`_elementor_data`) of any `elementskit_widget` custom post type by visiting a specially crafted URL. The widget's custom designs, text, and configurations are permanently replaced with a blank template.

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 confidence

The ElementsKit plugin has a missing capability check on the `Live_Action::reset()` function hooked to WordPress `init`. Unauthenticated attackers can trigger it by sending `post` and `action=elementor` GET parameters, which permanently overwrites `_elementor_data` in any `elementskit_widget` post with a blank template.

MitigationApply the vendor patch (upgrade to 3.8.3+) or implement web application firewall rules to block requests with the exploit parameters until the update is available.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify ElementsKit plugin is installed
    Check the WordPress plugins directory orwp-admin/plugins.php for the ElementsKit plugin. Alternatively, look for elementskit directory in wp-content/plugins/
    Affected if ElementsKit plugin is present in the WordPress installation
  2. Identify installed ElementsKit version
    Read the main plugin file (usually elementskit/elementskit.php or elementskit-lite/elementskit-lite.php) and locate the 'Version' header in the plugin comments. Compare this version number to 3.8.3
    Affected if Installed version is lower than 3.8.3 or the version cannot be determined
  3. Check for elementskit_widget post type content
    Query the WordPress database: SELECT * FROM wp_posts WHERE post_type='elementskit_widget' AND post_status='publish'; Or use WP CLI: wp post list --post_type=elementskit_widget --status=publish
    Affected if Any posts exist with post_type 'elementskit_widget' that contain saved widget data in post_content or meta _elementor_data
  4. Test vulnerable endpoint accessibility
    Send a crafted request: POST to any page with parameter action=elementor AND post parameter containing the reset trigger. Check if the response indicates the reset executed without authentication error
    Affected if The request executes without requiring authentication (returns 200 instead of 401/403) and modifies _elementor_data metadata
  5. Inspect _elementor_data for modification
    Query database before and after exploit test: SELECT ID, post_title FROM wp_posts WHERE post_type='elementskit_widget'; Then check meta: SELECT * FROM wp_postmeta WHERE meta_key='_elementor_data' AND post_id IN (IDs from previous query); Look for blank or empty _elementor_data values
    Affected if Any elementskit_widget posts have empty/blank _elementor_data that was not intentionally cleared

The environment is affected if ElementsKit plugin version is below 3.8.3 AND elementskit_widget posts exist in the database with non-empty _elementor_data that could be overwritten.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (upgrade to 3.8.3+) or implement web application firewall rules to block requests with the exploit parameters until the update is available.

Recommended fix Moderate confidence

ElementsKit Elementor Addons version 3.8.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the ElementsKit Elementor Addons plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify that the plugin functions correctly by checking your Elementor widgets

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4362 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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