dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-5614

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 Piotnet Addons For Elementor plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.4.29 via the 'pafe_posts_list' function. This makes it possible for unauthenticated attackers to extract sensitive data including titles and excerpts of future, draft, and pending blog posts.

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 Piotnet Addons For Elementor plugin for WordPress contains an information disclosure vulnerability in the 'pafe_posts_list' function. Unauthenticated attackers can exploit this to retrieve sensitive metadata including titles and excerpts from future, draft, and pending blog posts that should not be publicly accessible.

MitigationUpdate the Piotnet Addons For Elementor plugin to version 2.4.30 or later. If immediate patching is not possible, restrict access to the affected endpoint or disable the plugin until an update can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify Piotnet Addons For Elementor is installed
    Check the WordPress plugins directory at /wp-content/plugins/ for a folder named 'piotnet-addons-for-elementor' or query the wp_options table for the option_name 'active_plugins'
    Affected if The plugin folder or active plugin entry exists in WordPress
  2. Identify the installed plugin version
    Read the main plugin file header at /wp-content/plugins/piotnet-addons-for-elementor/piotnet-addons-for-elementor.php and locate the 'Version' comment, or query the wp_options table for option_name containing the plugin version
    Affected if The version number is lower than 2.4.30
  3. Confirm the vulnerable endpoint is accessible
    Test accessing the 'pafe_posts_list' AJAX endpoint by sending a POST request to /wp-admin/admin-ajax.php with action=pafe_posts_list, or check if the function pafe_posts_list is defined in the plugin files
    Affected if The endpoint responds without authentication or returns post data that includes draft, pending, or scheduled posts
  4. Check for sensitive post metadata exposure
    Review the response from the pafe_posts_list endpoint to see if it returns post statuses other than 'publish', specifically 'future', 'draft', or 'pending'
    Affected if The response contains titles, excerpts, or content from non-public posts (future, draft, or pending status)

If Piotnet Addons For Elementor is installed at a version below 2.4.30 AND the pafe_posts_list endpoint returns draft, pending, or scheduled posts without authentication, the environment is affected by this CVE.

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

Update the Piotnet Addons For Elementor plugin to version 2.4.30 or later. If immediate patching is not possible, restrict access to the affected endpoint or disable the plugin until an update can be applied.

Recommended fix High confidence

Piotnet Addons For Elementor version 2.4.30 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Piotnet Addons For Elementor' in the plugin list
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/piotnet-addons-for-elementor
  5. Verify the update completes successfully
  6. Confirm the plugin version is 2.4.30 or higher after updating

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

Have this fixed 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 help mitigating

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-2024-5614 — 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-5614 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