CVE-2026-7542: Slider Revolution WordPress plugin sensitive information disclosure

CVE-2026-7542 · Severity: medium · CVSS 6.5 · Published 2026-06-09

Slider Revolution, a popular WordPress plugin for creating visual content, contains a security flaw that allows low-level users to access sensitive server files. By exploiting a design error in how the plugin handles image imports, an attacker with a basic account can copy private files—such as configuration files, database backups, or security keys—into a public folder where they can be downloaded. This could lead to a full site takeover if sensitive credentials or database information are exposed.

Technologies: ThemePunch Slider Revolution. Vendors: ThemePunch.

Quick answers

Is CVE-2026-7542 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-7542 being exploited in the wild.
How severe is CVE-2026-7542?
Medium severity, with a CVSS score of 6.5, published 9 June 2026.
Which products and versions are affected?
ThemePunch Slider Revolution up to and including 7.0.10.
Is there a fix for CVE-2026-7542?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-7542 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-7542?
Check whether you run ThemePunch Slider Revolution at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability arises from three compounding flaws: a leaked AJAX nonce to all authenticated users, an allowlisted action that bypasses administrator-only checks, and a failure to restrict the 'url' parameter to remote protocols in the create_wordpress_image_from_url() function. Because the plugin uses path_or_url_exists() and @copy() without verifying if the source is a local filesystem path, authenticated attackers (Subscriber level and above) can force the server to copy local files into a publicly accessible directory. The exploit is further facilitated by a weak extension blacklist that fails to block sensitive file types like .sql, .pem, and .conf, and a MIME type check that relies on attacker-supplied input. Users should update to a version beyond 7.0.10.

Affected products

  • ThemePunch Slider Revolution up to and including 7.0.10

Timeline

  • 2026-06-09: disclosed
  • 2026-06-09: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.