Quick answers
- Is CVE-2026-75027 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75027 being exploited in the wild.
- How severe is CVE-2026-75027?
- Medium severity, with a CVSS score of 5.3, published 22 August 2026.
- Which products and versions are affected?
- Themify Builder up to 7.8.0.
- Is there a fix for CVE-2026-75027?
- 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-75027 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-75027?
- Check whether you run Themify 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 vulnerability is an authorization bypass in the Themify Builder plugin's styling handler, affecting versions up to 7.8.0. The root cause is insufficient authorization verification: the plugin fails to properly check whether a user has permission to modify post styling data before processing requests. Although the handler requires a nonce for CSRF protection, the nonce is automatically embedded in all frontend pages via wp_localize_script, allowing any unauthenticated visitor to extract a valid nonce from the page source. An attacker can then craft a request with an arbitrary post ID and JSON styling payload to modify stored builder data. Network reachability and the ability to view a public page are the only prerequisites; no prior authentication is required.
Affected products
- Themify Builder up to 7.8.0
Timeline
- 2026-08-22: disclosed