dbcve.org
ElementskitWordPress extension · Wpmet

CVE-2024-4404

CRITICAL · 9.6 CVSS v3.1 Published 2024-06-14
Fix available
A fix is available. Upgrade to 3.6.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 PRO plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 3.6.2 via the 'render_raw' function. This can allow authenticated attackers, with contributor-level permissions and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 PRO WordPress plugin contains an authenticated Server-Side Request Forgery (SSRF) vulnerability in the render_raw function. Attackers with contributor-level or higher permissions can make arbitrary web requests from the server, potentially accessing internal services and exfiltrating sensitive information.

MitigationUpgrade ElementsKit PRO to a version beyond 3.6.2 that contains the patched render_raw function with proper request validation and access controls.

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
ElementskitWordPress extension
Affected:< 3.6.3

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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. Confirm ElementsKit PRO is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the elementskit folder, or access WordPress admin > Plugins to list installed plugins. Identify if ElementsKit PRO (or Wpmet Elementskit) appears in the plugin list.
    Affected if The plugin is not found in the installed plugins list, then the environment is not affected by this specific vulnerability.
  2. Identify the installed version of ElementsKit PRO
    In WordPress admin, go to Plugins > Installed Plugins > ElementsKit PRO. The version number is displayed below the plugin name. Alternatively, check the main plugin file (elementskit/elementskit.php) for the 'Version' header in the plugin comments.
    Affected if The installed version is any version prior to 3.6.3 (e.g., 3.6.2, 3.6.1, 3.5.0, etc.), indicating the vulnerable version is present.
  3. Verify contributor or higher user roles exist
    In WordPress admin, navigate to Users > All Users. Review the role assigned to each user account. Identify whether any accounts have the Contributor, Author, Editor, or Administrator role.
    Affected if At least one user account with Contributor-level or higher permissions exists in the WordPress installation, which satisfies the authentication requirement for exploiting this SSRF flaw.
  4. Confirm the render_raw function is accessible
    Locate the render_raw function in the ElementsKit PRO codebase, typically found in the elementskit directory under includes or helpers. Check if the function processes user-supplied URLs without proper validation (requires code review or vulnerability scan of the specific file containing render_raw).
    Affected if The render_raw function accepts URL parameters and performs server-side requests without validating the destination, allowing the SSRF to be exploited.

The environment is affected if ElementsKit PRO version is below 3.6.3 AND contributor-level or higher user accounts exist, enabling an authenticated attacker to exploit the render_raw function for SSRF.

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 3.6.3 or later
Fixed in 3.6.3
Interim mitigation

Upgrade ElementsKit PRO to a version beyond 3.6.2 that contains the patched render_raw function with proper request validation and access controls.

Recommended fix High confidence

3.6.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate ElementsKit PRO in the plugin list
  4. Check if an update is available for ElementsKit PRO
  5. If an update is available, click 'Update Now' to update to version 3.6.3
  6. Alternatively, download ElementsKit PRO version 3.6.3 from the official source (wpmet.com) and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the current version is 3.6.3 or higher

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

Fix this in Elementskit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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