Path TraversalWeakness · CWE-22

CVE-2024-43281

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in VOID CODERS Void Elementor Post Grid Addon for Elementor Page builder allows PHP Local File Inclusion.This issue affects Void Elementor Post Grid Addon for Elementor Page builder: from n/a through 2.3.

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

A path traversal vulnerability in the Void Elementor Post Grid Addon for Elementor allows attackers to perform local file inclusion (LFI) by manipulating file paths. This could enable reading sensitive files or potentially executing arbitrary PHP code if an attacker can upload files to the server.

MitigationUpdate to the latest version of Void Elementor Post Grid Addon when available, implement strict input validation on file path parameters to prevent directory traversal sequences (../), and apply principle of least privilege to file system access.

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/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. Locate Void Elementor Post Grid Addon installation
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'void-elementor-post-grid' or similar, or view the installed plugins list via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin is installed and active in your WordPress environment
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins and find the Void Elementor Post Grid Addon entry; the version number is displayed below the plugin name. Alternatively, check the main plugin PHP file header for 'Version:' comment
    Affected if You cannot determine the version number or version is earlier than the patched release
  3. Check for file path parameter exposure
    Review your web server access logs for requests to pages using the Void Elementor Post Grid widget that contain path traversal sequences like '..' or absolute file paths in query parameters (e.g., ?file=../../wp-config.php)
    Affected if Such requests appear in your logs, indicating active probing of the vulnerability
  4. Inspect Elementor page templates
    In Elementor editor, search for any pages/posts using the 'Void Post Grid' or 'Post Grid' widget from this addon, then examine the widget settings for any file path, template, or include-related options that accept user input
    Affected if The widget exposes any parameter that accepts file path input without validation
  5. Verify file access permissions
    Check if the web server process has read access to sensitive files such as wp-config.php, .env files, or other configuration files in the document root
    Affected if The web server user can read these sensitive files and the vulnerable parameter is exposed

You are affected if Void Elementor Post Grid Addon is installed and any page uses a file path parameter that can be manipulated to traverse directories.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Void Elementor Post Grid Addon when available, implement strict input validation on file path parameters to prevent directory traversal sequences (../), and apply principle of least privilege to file system access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-43281 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