dbcve.org
Exclusive Addons For ElementorWordPress extension · Devscred

CVE-2022-45067

HIGH · 8.8 CVSS v3.1 Published 2023-02-02
Fix available
A fix is available. Upgrade to 2.6.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in DevsCred Exclusive Addons Elementor plugin <= 2.6.1 versions.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in DevsCred Exclusive Addons Elementor plugin version 2.6.1 and below allows attackers to induce authenticated users (likely administrators) to perform unintended actions via malicious requests. The lack of proper anti-CSRF token validation in the plugin's form submissions or admin actions enables this attack vector.

MitigationUpdate DevsCred Exclusive Addons Elementor plugin to the latest version available from the vendor, which should contain proper nonce validation and CSRF protection mechanisms.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Exclusive Addons For ElementorWordPress extension
Affected:< 2.6.2

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

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

  1. Verify plugin installation
    Access your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'DevsCred Exclusive Addons For Elementor' or 'Exclusive Addons for Elementor' in the list of installed plugins.
    Affected if The plugin is not found in the installed plugins list
  2. Check installed version
    In the WordPress plugins list, locate the DevsCred Exclusive Addons plugin and note the version number displayed beneath the plugin name. Compare this version against the affected range (2.6.1 and below).
    Affected if The installed version is 2.6.1 or any version lower than 2.6.2
  3. Identify active admin actions or forms
    Review the plugin settings and any custom post types or widgets created with this plugin that accept form submissions or perform administrative actions. Check if the plugin is used to create contact forms, submission forms, or admin configuration panels.
    Affected if The plugin is actively used to create or manage form submissions or admin configuration actions
  4. Inspect plugin source for nonce validation
    If you have file system access, locate the plugin directory (typically wp-content/plugins/exclusive-addons-for-elementor or similar) and examine PHP files that handle form submissions or admin actions. Look for the presence of nonce verification calls such as wp_verify_nonce, check_admin_referer, or check_ajax_referer in form handling code.
    Affected if No nonce validation is found in the plugin's form handling or admin action files

Your environment is affected if DevsCred Exclusive Addons For Elementor is installed with version 2.6.1 or below and is actively used for form submissions or admin actions lacking CSRF token validation.

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
Upgrade available Upgrade to 2.6.2 or later
Fixed in 2.6.2
Interim mitigation

Update DevsCred Exclusive Addons Elementor plugin to the latest version available from the vendor, which should contain proper nonce validation and CSRF protection mechanisms.

Recommended fix High confidence

2.6.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Exclusive Addons For Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 2.6.2 or later from the WordPress plugin repository and upload it
  5. Verify the updated version number reflects 2.6.2 or higher after the update completes

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

Fix this in Exclusive Addons For Elementor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45067 — 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-2022-45067 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