CVE-2026-7542 Slider Revolution 7.0 - 7.0.10 - Authenticated (Subscriber+) Sensitive Information Disclosure
Authenticated subscribers can read sensitive server files by exploiting path traversal and weak validation in the Slider Revolution WordPress plugin.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-7542?
CVE-2026-7542 is a medium-severity vulnerability in Slider Revolution, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The Slider Revolution plugin for WordPress is vulnerable to Sensitive Information Disclosure in versions 7.0 to 7.0.10. This is due to three compounding design flaws: (1) the plugin leaks a valid backend AJAX nonce (revslider_actions) to all authenticated users including Subscribers via the admin_footer hook; (2) the wordpress.create.image_from_url action is explicitly allowlisted in the $user_allowed array, bypassing the administrator-only access control; (3) the create_wordpress_image_from_url() function accepts an attacker-controlled url parameter that is passed to import_media(), where path_or_url_exists() explicitly accepts local filesystem paths (file_exists() && is_readable()) with no restriction to remote HTTP/HTTPS URLs, and @copy() physically copies those files into the publicly accessible /wp-content/uploads/revslider/ai/ directory. The MIME type check trusts the attacker-supplied content_type parameter to derive the destination extension without verifying actual file content, and the source extension blacklist does not block many sensitive types (.sql, .log, .json, .bak, .xml, .csv, .conf, .yml, .yaml, .pem, .key, .crt, .txt, .db, etc.). This makes it possible for authenticated attackers with Subscriber-level access and above to read the contents of server files with non-blacklisted extensions by having them copied to a publicly accessible URL.
Weakness: CWE-200
Which versions are affected by CVE-2026-7542?
How do I fix CVE-2026-7542?
No fix has been published for CVE-2026-7542 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-7542 being exploited?
There is no known exploitation of CVE-2026-7542 in the wild and no public exploit code.
Sources
Also known as GHSA-gjww-c2x7-4348.