Is CVE-2026-39710 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-39710 being exploited in the wild.

How severe is CVE-2026-39710?

Medium severity, with a CVSS score of 5.4, 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-39710?

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-39710 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-39710?

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.

CVE-2026-39710: stmcan RT-Theme 18 Extensions CSRF

Q: Is there a fix for CVE-2026-39710?

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.

Q: How is CVE-2026-39710 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-39710?

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.

CVE-2026-39710 · Severity: medium · CVSS 5.4 · Published 2026-04-08

The RT-Theme 18 Extensions plugin for WordPress is vulnerable to a security flaw that could allow an attacker to trick an administrator into performing unintended actions. By enticing a logged-in user to click a malicious link or visit a specific webpage, an attacker could modify site settings or perform administrative tasks without the user's consent. This could lead to unauthorized changes to the website's configuration or content.

Technologies: Stmcan RT-Theme 18 Extensions. Vendors: Stmcan.

Quick answers

Is CVE-2026-39710 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-39710 being exploited in the wild.
How severe is CVE-2026-39710?: Medium severity, with a CVSS score of 5.4, 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-39710?: 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-39710 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-39710?: 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 Cross-Site Request Forgery (CSRF) vulnerability exists in the stmcan RT-Theme 18 | Extensions (rt18-extensions) plugin for WordPress through version 2.5. The vulnerability is caused by a lack of proper nonce validation or equivalent CSRF protections on sensitive administrative functions. An unauthenticated remote attacker can exploit this by tricking a privileged user (such as an administrator) into visiting a malicious website or clicking a crafted link while authenticated to the WordPress site. Successful exploitation allows the attacker to execute unauthorized actions on behalf of the victim, potentially altering site configurations. As of the advisory date, no official patch has been released.

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

References

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