Skip to main content

RT-Theme 18 CVE-2026-57745

| EUVDEUVD-2026-43388 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-07-13 Patchstack
7.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious link to rt18-extensions parameter
  2. Delivery
    Deliver crafted URL via phishing
  3. Exploit
    Victim clicks and loads reflected page
  4. Execution
    Injected script executes in victim browser
  5. Impact
    Hijack session or act as victim

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the RT-Theme 18 | Extensions plugin (version ≤ 2.5) to be installed and active on the WordPress site, and - per CVSS UI:R - requires a victim to interact by loading an attacker-crafted request (e.g., clicking a malicious link) that carries the reflected XSS payload into the vulnerable parameter. No authentication is needed by the attacker (PR:N) and the vector is network-reachable with low complexity (AV:N/AC:L), but the mandatory user interaction is the key limiting factor: the attack cannot fire without a targeted user visiting the crafted URL, and impact is bounded by that victim's browser context and privileges. The specific vulnerable parameter/endpoint is not named in the provided data.

Impact

The signals paint a moderate, user-interaction-gated risk rather than an urgent internet-wide threat. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, base 7.1) shows a network-reachable, low-complexity, unauthenticated flaw, but the UI:R requirement means a victim must click a crafted link, which substantially limits mass automation. The scope change (S:C) and Low impacts across confidentiality, integrity, and availability reflect typical reflected-XSS consequences (session-context script execution) rather than direct server compromise. No EPSS score, KEV listing, POC, or SSVC decision data was provided in the input, so exploitation probability cannot be quantified; the absence of KEV and POC signals suggests this is not known to be actively exploited. This is a real hygiene issue worth patching, but not a drop-everything priority absent evidence of exploitation.

Exploit ScenarioDerived

An attacker crafts a URL to the vulnerable rt18-extensions endpoint containing a malicious script payload in a reflected parameter and delivers it to a logged-in site user or administrator via phishing email or a malicious link. When the victim clicks, the script executes in their browser under the site's origin, allowing session/cookie theft or actions performed as the victim; the low attack complexity makes crafting the payload straightforward, though the required user interaction limits scale. No public POC is noted in the input.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 13, 2026

Reflected cross-site scripting in the stmcan RT-Theme 18 | Extensions WordPress plugin (all versions up to and including 2.5) lets remote attackers inject arbitrary JavaScript that executes in a victim's browser when they follow a crafted link. Because the CVSS scope is changed (S:C), a successful payload can affect resources beyond the vulnerable component, such as the WordPress session context. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV; disclosure comes from Patchstack.

RemediationAI

No vendor-released patch version is identified in the available data (the advisory documents affected versions up to and including 2.5 without naming a fixed build), so administrators should monitor the Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/rt18-extensions/vulnerability/wordpress-rt-theme-18-extensions-plugin-2-5-reflected-cross-site-scripting-xss-vulnerability and the stmcan/RT-Theme 18 vendor channel for an update newer than 2.5 and apply it as the primary fix. As compensating controls until a patch is available, deploy a WordPress-aware WAF or the Patchstack virtual-patch rule to filter the reflected XSS payload (trade-off: possible false positives on legitimate parameter values), enforce a strict Content-Security-Policy that disallows inline script execution to blunt reflected payloads (trade-off: may break theme features that rely on inline scripts), and consider disabling or restricting access to the affected extensions endpoint if the feature is not in use. These reduce exposure but do not remove the underlying flaw.

Affected VersionsENISA

RT-Theme 18 | Extensions 0 ≤2.5

Affected Packages

euvd rt_theme_18_extensions no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is rt18-extensions, the companion extensions plugin for the commercial RT-Theme 18 WordPress theme by stmcan, identified by CPE cpe:2.3:a:stmcan:rt-theme_18_|_extensions. The root cause is CWE-79, Improper Neutralization of Input During Web Page Generation: user-controllable request input is reflected back into an HTML response without adequate output encoding or input sanitization, so a browser interprets attacker-supplied markup as executable script. As a reflected variant, the payload is not stored server-side but is delivered within the request itself (typically a URL parameter) and echoed into the generated page, meaning exploitation requires the victim to load an attacker-crafted request.

Know when Rt Theme 18 Extensions gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 7.1 HIGH

Reflected XSS is network-reachable and low-complexity with no attacker auth (PR:N) but needs victim click (UI:R); scope changes into browser context (S:C) with limited C/I/A impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

DescriptionCVE.org

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in stmcan RT-Theme 18 | Extensions rt18-extensions allows Reflected XSS.This issue affects RT-Theme 18 | Extensions: from n/a through <= 2.5.

Executive ViewAI

Why It Matters

The stmcan RT-Theme 18 Extensions WordPress plugin (all versions through 2.5) contains a reflected cross-site scripting vulnerability that enables attackers to inject malicious scripts into user browsers via crafted links, potentially hijacking WordPress sessions and compromising site administration. Organizations using this plugin expose their WordPress installations to credential theft, unauthorized administrative access, and data exfiltration affecting both administrators and end users.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) deactivate the plugin and replace with a maintained alternative; (2) implement strict Content Security Policy headers to block inline script execution; (3) deploy Web Application Firewall rules targeting reflected XSS patterns; (4) enforce multi-factor authentication on WordPress administrator accounts to limit session hijacking impact; (5) monitor WordPress security logs and audit trails for exploit activity.

Threat Intelligence Overview

EPSS Score
0.3%
Top 84% exploitable
Prevalence
Low
extensions plugin for a single commercial WordPress theme, niche footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy