Quick answers
- Is CVE-2026-81564 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81564 being exploited in the wild.
- How severe is CVE-2026-81564?
- Informational severity, published 14 September 2026.
- Which products and versions are affected?
- JoomShaper SP Page Builder 4.0.0 to 6.9.0.
- Is there a fix for CVE-2026-81564?
- 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-81564 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-81564?
- Check whether you run JoomShaper SP Page Builder 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 media rename task in SP Page Builder (versions 4.0.0 to 6.9.0) fails to implement proper directory boundary checks and validates only that either a media record exists or the path is present in the database, without verifying they match. The STR input filter leaves path traversal sequences intact, allowing an attacker to pair any valid media identifier with an unrelated filesystem path and rename files outside the intended directory. An attacker could rename critical files such as configuration.php to disable the site. The vulnerability requires authentication and access to the media rename functionality, but no patch information is currently available.
Affected products
- JoomShaper SP Page Builder 4.0.0 to 6.9.0
Timeline
- 2026-09-14: disclosed