Quick answers
- Is CVE-2026-39711 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39711 being exploited in the wild.
- How severe is CVE-2026-39711?
- Medium severity, with a CVSS score of 5.3, published 8 April 2026.
- Which products and versions are affected?
- stmcan RT-Theme 18 | Extensions (rt18-extensions) <= 2.5.
- Is there a fix for CVE-2026-39711?
- 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-39711 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-39711?
- Check whether you run Stmcan RT-Theme 18 Extensions. 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
A sensitive data exposure vulnerability (CWE-201) exists in the stmcan RT-Theme 18 | Extensions (rt18-extensions) plugin for WordPress. The flaw occurs due to the improper insertion of sensitive information into data sent by the application, which allows unauthenticated remote attackers to retrieve embedded sensitive data. The attack can be performed over the network without any user interaction. As of the advisory date, no official patch has been released for versions up to and including 2.5.
Affected products
- stmcan RT-Theme 18 | Extensions (rt18-extensions) <= 2.5
Timeline
- 2026-01-31: other: Vulnerability reported by researcher Bonds
- 2026-03-02: advisory: Initial advisory published by Patchstack
- 2026-04-08: disclosed: CVE published to NVD