dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-33634

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/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
Server-Side Request Forgery (SSRF) vulnerability in Piotnet Piotnet Addons For Elementor Pro.This issue affects Piotnet Addons For Elementor Pro: from n/a through 7.1.17.

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

Server-Side Request Forgery (SSRF) in Piotnet Addons for Elementor Pro allows an attacker to make the server perform requests to arbitrary internal or external URLs, potentially accessing internal services, cloud metadata endpoints, or bypassing firewall restrictions. The vulnerability stems from insufficient validation of user-controlled URL parameters in the plugin.

MitigationUpgrade to the latest version of Piotnet Addons for Elementor Pro once a patched release is available. Until then, restrict access to the plugin's admin interfaces and consider network-level filtering to block outgoing requests from the web server to sensitive internal resources.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/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 Piotnet Addons for Elementor Pro is installed
    Navigate to WordPress admin > Plugins and look for 'Piotnet Addons for Elementor Pro' in the installed plugins list, or check the wp-content/plugins directory for a folder starting with 'piotnet'
    Affected if The plugin appears in the installed plugins list and is activated
  2. Identify the installed version number
    In WordPress admin > Plugins, click on the plugin name to view details and note the version number displayed, or check the main plugin PHP file for a 'Version' constant
    Affected if The installed version is lower than the patched release (compare against any release notes or changelog once available)
  3. Check for exposed URL submission features
    Review the website frontend and Elementor editor for any Piotnet widgets or forms that accept URL input, particularly any features labeled as API fetcher, external request, URL preview, or similar URL-handling functionality
    Affected if A Piotnet widget or form that accepts user-supplied URLs is published and accessible to visitors or authenticated users
  4. Verify the plugin admin settings for URL-related options
    Go to Piotnet Addons settings in the WordPress admin panel and inspect any sections related to API connections, webhooks, URL requests, or external integrations
    Affected if URL-related settings are enabled or configurable without admin-only restrictions
  5. Test for SSRF vulnerability with a benign request
    If a URL input field is found, submit a URL pointing to an internal address (such as http://localhost or the server's internal IP) and observe whether the server attempts to fetch it (this should only be done in authorized, non-production environments)
    Affected if The server successfully processes requests to internal addresses, indicating the SSRF vulnerability is present

A user is affected if Piotnet Addons for Elementor Pro is installed with a version lacking the patch, AND a URL-handling feature is accessible to users.

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

Upgrade to the latest version of Piotnet Addons for Elementor Pro once a patched release is available. Until then, restrict access to the plugin's admin interfaces and consider network-level filtering to block outgoing requests from the web server to sensitive internal resources.

Recommended fix Moderate confidence

Version newer than 7.1.17 (latest stable release)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate Piotnet Addons For Elementor Pro
  4. 4. Check the current installed version to confirm it is 7.1.17 or earlier
  5. 5. Update the plugin to the latest available version which contains the security fix for CVE-2024-33634
  6. 6. Verify the update was successful and test Elementor page builder functionality
Caveat Review plugin changelog for any breaking changes between your current version and the target version, particularly if skipping multiple version numbers

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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