CVE-2026-9048
Sensitive Information Exposure in Slider Revolution WordPress Plugin
Publication date: 2026-06-02
Last updated on: 2026-06-02
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| slider_revolution | slider_revolution | From 7.0.0 (inc) to 7.0.14 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Slider Revolution plugin for WordPress, versions 7.0.0 to 7.0.14, has a vulnerability in the 'slider.get.full' AJAX action. This flaw allows authenticated attackers with Contributor-level access or higher to extract sensitive information.
- Attackers can obtain raw social media API credentials such as the Instagram OAuth token, Flickr API key, YouTube Data API key, and Facebook App ID.
These credentials are stored in the settings of any configured slider, making them accessible through this vulnerability.
How can this vulnerability impact me? :
This vulnerability can lead to sensitive information exposure, specifically leaking social media API credentials.
- An attacker with Contributor-level access could misuse these credentials to access or manipulate social media accounts or services linked to the affected plugin.
- Such exposure could result in unauthorized actions on social media platforms, data breaches, or further exploitation of connected systems.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability in the Slider Revolution plugin, you should update the plugin to the latest patched version beyond 7.0.14.
Additionally, follow security best practices such as limiting Contributor-level access, monitoring for unauthorized access, and reviewing slider settings for exposed sensitive data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in the Slider Revolution plugin allows authenticated attackers with Contributor-level access and above to extract sensitive data, including raw social media API credentials such as Instagram OAuth tokens, Flickr API keys, YouTube Data API keys, and Facebook App IDs.
Exposure of such sensitive information could potentially lead to unauthorized access or misuse of personal or organizational data, which may impact compliance with data protection regulations like GDPR or HIPAA that require safeguarding sensitive information.
However, the provided information does not explicitly describe the direct impact on compliance with these standards or any regulatory consequences.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves the Slider Revolution WordPress plugin versions 7.0.0 to 7.0.14 and can be exploited via the 'slider.get.full' AJAX action by authenticated users with Contributor-level access or higher.
To detect if your system is vulnerable, you should first verify the version of the Slider Revolution plugin installed on your WordPress site. If it falls within the affected range, the site is potentially vulnerable.
You can check the plugin version by running the following command on your server (assuming you have shell access and the WordPress installation path):
- grep 'Version:' wp-content/plugins/revslider/revslider.php
Alternatively, you can query the plugin version via WP-CLI:
- wp plugin get revslider --field=version
To detect exploitation attempts on your network, monitor HTTP requests for the AJAX action 'slider.get.full' originating from authenticated users. For example, using command-line tools like grep on your web server logs:
- grep 'action=slider.get.full' /var/log/apache2/access.log
- grep 'action=slider.get.full' /var/log/nginx/access.log
Look for requests that include this AJAX action and check if they come from users with Contributor-level or higher privileges.