CVE-2026-1988
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 · uneditedThe Flexi Product Slider and Grid for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.0.5 via the `flexipsg_carousel` shortcode. This is due to the `theme` parameter being directly concatenated into a file path without proper sanitization or validation, allowing directory traversal. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary PHP files on the server via the `theme` parameter granted they can create posts with shortcodes.
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 confidenceThe Flexi Product Slider and Grid for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion (LFI) in versions up to 1.0.5. The vulnerability exists in the `flexipsg_carousel` shortcode where the `theme` parameter is directly concatenated into a file path without sanitization or validation, enabling directory traversal attacks.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Flexi Product Slider and Grid for WooCommerce'. Check the version number displayed below the plugin name.Affected if The plugin is installed and the version is 1.0.5 or lower (any version up to and including 1.0.5).
-
Identify usage of the vulnerable shortcodeSearch your WordPress database for instances of the 'flexipsg_carousel' shortcode. This can be done via phpMyAdmin with a query like: SELECT * FROM wp_posts WHERE post_content LIKE '%flexipsg_carousel%' (replace wp_ with your table prefix).Affected if Any post, page, or widget contains the flexipsg_carousel shortcode with a theme parameter present.
-
Inspect the theme parameter in shortcodesExamine any found shortcodes for the 'theme' attribute, for example: [flexipsg_carousel theme="..."]. The vulnerability allows directory traversal if the theme value contains path traversal sequences like ../Affected if The flexipsg_carousel shortcode includes a theme parameter, as this parameter is the direct entry point for the LFI flaw.
Your environment is affected if the Flexi Product Slider and Grid for WooCommerce plugin versions up to 1.0.5 are installed AND the flexipsg_carousel shortcode with a theme parameter is in use on your site.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of the plugin. Until a fix is available, restrict or disable Contributor-level and above users' ability to create or edit posts containing shortcodes to prevent exploitation of this LFI vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1988 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1988 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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