CVE-2025-15491
Local File Inclusion in Post Slides WordPress Plugin
Publication date: 2026-02-07
Last updated on: 2026-02-09
Assigner: WPScan
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| post_slides | post_slides | to 1.0.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2025-15491 is a Local File Inclusion (LFI) vulnerability in the WordPress plugin "Post Slides" version 1.0.1 and earlier. The plugin does not properly validate certain shortcode attributes before using them to build file paths that are passed to PHP include functions.'}, {'type': 'paragraph', 'content': 'This flaw allows any authenticated user with contributor-level permissions or higher to manipulate shortcode attributes to include arbitrary files from the server. For example, an attacker can include sensitive files like wp-config.php by crafting a shortcode that points to that file.'}, {'type': 'paragraph', 'content': 'The vulnerability is classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) and is considered an injection flaw according to OWASP Top 10 A1.'}] [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive files on the server by allowing authenticated users with contributor or higher roles to include arbitrary files.
An attacker could exploit this to access critical configuration data such as database credentials stored in files like wp-config.php, potentially leading to further compromise of the website or server.
Since the vulnerability allows file inclusion, it may also be leveraged to execute malicious code if combined with other vulnerabilities or misconfigurations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by checking for the presence of the vulnerable Post Slides WordPress plugin version 1.0.1 or earlier installed on your system.'}, {'type': 'paragraph', 'content': 'Additionally, detection can involve searching for posts or content containing manipulated shortcode attributes that attempt Local File Inclusion (LFI) attacks, such as shortcodes like `[post-slides skin="../../../../wp-config"]`.'}, {'type': 'paragraph', 'content': 'You can use commands to search your WordPress content database or files for suspicious shortcode usage. For example, using WP-CLI to search posts:'}, {'type': 'list_item', 'content': 'wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE \'%[post-slides skin=%\'"'}, {'type': 'paragraph', 'content': 'Or using grep on the WordPress content directory to find suspicious shortcode usage:'}, {'type': 'list_item', 'content': "grep -r '\\[post-slides skin=' /path/to/wordpress/wp-content/"}, {'type': 'paragraph', 'content': 'Also, verify the plugin version installed by checking the plugin directory or using WP-CLI:'}, {'type': 'list_item', 'content': 'wp plugin list | grep post-slides'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Since there is currently no known fix for this vulnerability, immediate mitigation steps include:
- Restrict authenticated user roles to only trusted users, especially limiting contributor or higher roles to trusted personnel.
- Remove or deactivate the vulnerable Post Slides plugin version 1.0.1 or earlier until a patch or update is released.
- Monitor your WordPress site for suspicious shortcode usage that attempts to exploit the LFI vulnerability.
- Implement additional security measures such as Web Application Firewalls (WAF) to detect and block malicious shortcode payloads.