CVE-2026-39710 | stmcan RT-Theme 18 Plugin up to 2.5 on WordPress cross-site request forgery (EUVD-2026-20417)
VulDBArchived Apr 08, 2026✓ Full text saved
A vulnerability, which was classified as problematic , was found in stmcan RT-Theme 18 Plugin up to 2.5 on WordPress. This affects an unknown part. Such manipulation leads to cross-site request forgery. This vulnerability is traded as CVE-2026-39710 . The attack may be launched remotely. There is no exploit available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-356205 · CVE-2026-39710 · EUVD-2026-20417
STMCAN RT-THEME 18 PLUGIN UP TO 2.5 ON WORDPRESS CROSS-SITE REQUEST FORGERY
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.2 $0-$5k 1.72+
Summaryinfo
A vulnerability has been found in stmcan RT-Theme 18 Plugin up to 2.5 on WordPress and classified as problematic. This vulnerability affects unknown code. Performing a manipulation results in cross-site request forgery. This vulnerability is known as CVE-2026-39710. Remote exploitation of the attack is possible. No exploit is available.
Detailsinfo
A vulnerability, which was classified as problematic, was found in stmcan RT-Theme 18 Plugin up to 2.5 on WordPress. This affects an unknown part. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:
Cross-Site Request Forgery (CSRF) vulnerability in stmcan RT-Theme 18 | Extensions rt18-extensions allows Cross Site Request Forgery.This issue affects RT-Theme 18 | Extensions: from n/a through <= 2.5.
The weakness was published by Bonds. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2026-39710 since 04/07/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-20417).
Productinfo
Type
WordPress Plugin
Vendor
stmcan
Name
RT-Theme 18 Plugin
Version
2.0
2.1
2.2
2.3
2.4
2.5
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Cross-site request forgery
CWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/07/2026 CVE reserved
04/08/2026 +1 days Advisory disclosed
04/08/2026 +0 days VulDB entry created
04/08/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: patchstack.com
Researcher: Bonds
Status: Not defined
CVE: CVE-2026-39710 (🔒)
GCVE (CVE): GCVE-0-2026-39710
GCVE (VulDB): GCVE-100-356205
EUVD: 🔒
Entryinfo
Created: 04/08/2026 12:58
Updated: 04/08/2026 13:23
Changes: 04/08/2026 12:58 (55), 04/08/2026 13:23 (1)
Complete: 🔍
Cache ID: 99:737:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸