dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-8392

HIGH · 7.2 CVSS v3.1 Published 2024-10-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 WordPress Post Grid Layouts with Pagination – Sogrid plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.5.6 via the 'tab' parameter. This makes it possible for authenticated attackers, with Administrator-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. This can also be exploited via CSRF techniques.

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 Sogrid WordPress plugin versions 1.5.6 and below contain a Local File Inclusion vulnerability via the 'tab' parameter. Authenticated attackers with Administrator-level access can manipulate this parameter to include and execute arbitrary files on the server, leading to potential code execution. The vulnerability can also be exploited via CSRF.

MitigationUpdate to version 1.5.7 or later which contains the patch. Alternatively, implement strict input validation on the 'tab' parameter to prevent path traversal sequences, restricting inclusion to only expected, safe values.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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. Confirm WordPress installation
    Identify if the target website runs on WordPress CMS (check for wp-content, wp-admin directories, or HTML source for WordPress markers)
    Affected if The target is not a WordPress site (this CVE does not apply)
  2. Check if Sogrid plugin is installed
    Locate the Sogrid plugin in the WordPress plugin directory (wp-content/plugins/) or list installed plugins via WordPress admin panel or database
    Affected if Sogrid plugin is not installed on the WordPress environment
  3. Determine installed Sogrid version
    Read the main plugin file header (typically main PHP file in plugin directory) to extract the Version field, or query the wp_options table for the active_plugins entry
    Affected if The installed version is 1.5.6 or lower (versions 1.5.6 and below are affected)
  4. Verify plugin is active
    Check WordPress admin under Plugins > Installed Plugins to confirm Sogrid status, or query wp_options for active_plugins containing sogrid
    Affected if The plugin is active and the version is 1.5.6 or below - the vulnerability is exploitable
  5. Confirm Administrator-level accounts exist
    Review user role capabilities in wp_users and wp_usermeta tables, or check WordPress admin Users section for accounts with Administrator role
    Affected if Administrator accounts exist and the plugin version is 1.5.6 or below - exploitation is possible with compromised admin credentials or via CSRF attack vector

A WordPress environment with Sogrid plugin versions 1.5.6 or below installed and active is affected by this Local File Inclusion vulnerability.

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 to version 1.5.7 or later which contains the patch. Alternatively, implement strict input validation on the 'tab' parameter to prevent path traversal sequences, restricting inclusion to only expected, safe values.

Recommended fix High confidence

Version 1.5.7 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WordPress Post Grid Layouts with Pagination – Sogrid' plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload it
  5. Verify the plugin updated to version 1.5.7 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-8392 — 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-8392 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