CVE-2026-1988
Local File Inclusion in Flexi Product Slider Plugin Allows Code Execution
Publication date: 2026-02-14
Last updated on: 2026-02-14
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wpbeaverbuilder | flexi_product_slider_and_grid_for_woocommerce | to 1.0.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-98 | The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
The vulnerability in CVE-2026-1988 affects the Flexi Product Slider and Grid plugin for WooCommerce on WordPress, specifically versions up to and including 1.0.5. It is a Local File Inclusion (LFI) vulnerability caused by improper handling of the `theme` parameter in the `flexipsg_carousel` shortcode.
Because the `theme` parameter is directly concatenated into a file path without proper sanitization or validation, an authenticated attacker with Contributor-level access or higher can exploit directory traversal to include and execute arbitrary PHP files on the server. This is possible if the attacker can create posts containing the shortcode with a manipulated `theme` parameter.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized execution of arbitrary PHP code on the server hosting the WordPress site.
- Attackers can leverage the vulnerability to execute malicious code, potentially leading to full system compromise.
- It can compromise the confidentiality, integrity, and availability of the application and underlying server.
- Attackers with Contributor-level access can escalate their privileges or perform unauthorized actions by injecting and running PHP files.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves exploitation of the `flexipsg_carousel` shortcode in the Flexi Product Slider and Grid for WooCommerce plugin by manipulating the `theme` parameter to include arbitrary PHP files via directory traversal. Detection involves monitoring for unusual shortcode usage or attempts to include unexpected files.
To detect exploitation attempts on your WordPress site, you can search for posts or content containing the `[flexipsg_carousel]` shortcode with suspicious `theme` parameter values that include directory traversal patterns such as "../".
- Use WP-CLI or database queries to find posts containing the shortcode with suspicious parameters, for example:
- wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[flexipsg_carousel%theme=%../%'"
- Check web server logs for requests containing the shortcode or attempts to access unusual theme files.
- Monitor for PHP errors or warnings related to missing or unexpected theme files in the plugin's templates directory.
Since the vulnerability requires authenticated users with Contributor-level access or higher to create posts with malicious shortcodes, auditing user activity and post creation logs for suspicious shortcode insertions can also help detect exploitation.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Update the Flexi Product Slider and Grid for WooCommerce plugin to a version later than 1.0.5 where the vulnerability is fixed.
- Restrict or review user permissions to ensure only trusted users have Contributor-level access or higher, as exploitation requires authenticated users with such privileges.
- Audit existing posts for malicious shortcodes using the `flexipsg_carousel` shortcode with suspicious `theme` parameters and remove or sanitize them.
- Implement strict input validation and sanitization on shortcode parameters, especially the `theme` parameter, to prevent directory traversal or file inclusion.
- Consider disabling or restricting the use of shortcodes that allow file inclusion until a patch is applied.
- Harden the server environment by running PHP with least privileges, disabling dangerous PHP features like `allow_url_fopen`, and restricting file system access to plugin directories.
- Use application firewalls or security plugins to detect and block attempts to exploit file inclusion or path traversal vulnerabilities.