dbcve.org
Grid PlusWordPress extension · G5theme

CVE-2023-5250

HIGH · 8.8 CVSS v3.1 Published 2023-10-30
Fix available
A fix is available. Upgrade to after 1.3.2 or later.
See remediation →
94/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 Grid Plus plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 1.3.3 via a shortcode attribute. This allows subscriber-level, and above, attackers 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 PHP files with arbitrary content can be uploaded and included.

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 Grid Plus WordPress plugin versions 1.3.3 and below are vulnerable to Local File Inclusion via a shortcode attribute. Authenticated attackers with subscriber-level privileges can exploit this by manipulating the shortcode to include arbitrary files, enabling execution of any PHP code present in those files.

MitigationUpdate Grid Plus plugin to version 1.4.0 or later. If update is unavailable, disable the plugin until a fix is released. Review user permissions to ensure untrusted users cannot access shortcode functionality.

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
Grid PlusWordPress extension
Affected:<= 1.3.2

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Grid Plus plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Grid Plus' or 'G5theme Grid Plus'. Note the installed version number displayed there.
    Affected if The plugin is present and active on the WordPress site
  2. Check installed version against affected range
    Compare the version number you found in the plugins list to the affected range: version 1.3.2 or lower.
    Affected if Installed version is 1.3.2 or lower, or any version shown as 1.3.3 (the summary indicates 1.3.3 and below are vulnerable)
  3. Confirm shortcode is accessible
    Test if the plugin shortcode (typically [grid_plus] or similar) is rendered on any public-facing post or page, or check the plugin settings to confirm shortcode functionality is enabled.
    Affected if The shortcode is active and can be used in posts or pages visible to authenticated users
  4. Identify subscriber-level users
    Go to Users > All Users in WordPress admin and review the list for any users with the 'Subscriber' role.
    Affected if There are one or more users with subscriber-level privileges who can access the shortcode

The site is affected if Grid Plus plugin version 1.3.2 or lower is installed, the shortcode is functional, and at least one subscriber-level user account exists.

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 a release after 1.3.2
Interim mitigation

Update Grid Plus plugin to version 1.4.0 or later. If update is unavailable, disable the plugin until a fix is released. Review user permissions to ensure untrusted users cannot access shortcode functionality.

Recommended fix Moderate confidence

Grid Plus plugin version 1.3.4 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Grid Plus plugin in the list
  4. Click 'Update Now' if an update is available, or manually upload the latest version from wordpress.org/plugins/grid-plus/
  5. Verify the plugin updated successfully to the latest version (above 1.3.3)
  6. Test that the plugin functionality works as expected

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

Fix this in Grid Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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