Skip to main content

Streamit WordPress theme CVE-2026-13423

| EUVDEUVD-2026-50115 CRITICAL
Code Injection (CWE-94)
2026-07-29 WPScan GHSA-fvvp-v9c4-343h
9.8
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

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

  1. Access
    Identify site running Streamit theme
  2. Delivery
    Send crafted POST to admin-ajax.php nopriv action
  3. Exploit
    Supply PHP function and argument array
  4. Execution
    Invoke wp_create_user to add admin
  5. Persist
    Execute arbitrary code / install webshell
  6. Impact
    Full site takeover

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

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

Exploitation Conditions

Exploitation requires only that the site run the Streamit theme (version ≤4.5.0) with its vulnerable unauthenticated AJAX route registered and reachable via /wp-admin/admin-ajax.php - the default state for the affected versions. No authentication, no user interaction, and no non-default configuration are needed (PR:N/UI:N/AC:L), and the attacker fully controls both the invoked PHP function name and its argument array. The only real limiting factors are that the target must actually have the Streamit theme active and internet-reachable, and any WAF or access control filtering the specific admin-ajax action would blunt the attack.

Impact

All signals point to genuine high priority: the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes network-reachable, low-complexity, unauthenticated exploitation with high confidentiality, integrity and availability impact, and publicly available exploit code lowers the barrier further. The vulnerability class - arbitrary PHP function invocation from an unauthenticated endpoint - is trivially automatable and self-contained, consistent with an SSVC 'automatable=yes / technical impact=total' reading. The main tempering factor is deployment footprint rather than exploitability: Streamit is a niche commercial theme, so exposure is limited by how many sites run it, not by attacker effort. No EPSS score or KEV status was provided in the input, so exploitation-probability and active-exploitation signals are unconfirmed here; the risk assessment rests on the CVSS vector, the code-injection root cause, and confirmed POC availability rather than on EPSS/KEV.

Exploit ScenarioDerived

An attacker sends a single crafted POST request to /wp-admin/admin-ajax.php targeting the vulnerable nopriv action, supplying a PHP function name (e.g. a user-creation function) and an argument array that provisions a new administrator account. With that account or the code-execution primitive, the attacker logs in, installs a malicious plugin or webshell, and takes over the site - and because working exploit code is publicly available, this requires little skill or reconnaissance.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jul 29, 2026

Unauthenticated remote code execution in the Streamit WordPress theme (versions up to and including 4.5.0) stems from a missing-authorization AJAX endpoint that invokes an attacker-supplied PHP function with attacker-supplied arguments, letting unauthenticated attackers create administrator accounts and run arbitrary code. Reported by WPScan and tracked as EUVD-2026-50115, it carries a CVSS 9.8 and publicly available exploit code exists, though there is no public exploit identified as being used in active attacks at time of analysis.

RemediationAI

No specific vendor-released patched version is identified in the provided data, so no vendor-released patch is confirmed at time of analysis; consult the WPScan advisory (https://wpscan.com/vulnerability/f85c5da1-412f-4079-8c44-708bc78c2b9b/) and the theme vendor/ThemeForest listing for a release above 4.5.0 and upgrade to it as the primary fix once available. As compensating controls, block or restrict the vulnerable unauthenticated action by adding a WAF/mod_security rule that filters the specific admin-ajax.php action parameter used by this route (trade-off: requires identifying the exact action name from the WPScan writeup and may break legitimate theme AJAX features), restrict access to /wp-admin/admin-ajax.php at the reverse proxy where feasible without breaking front-end functionality, and audit wp_users for unexpected administrator accounts created since exposure, rotating credentials and reviewing installed plugins/files for webshells. If a patched release is not promptly available, switching to an alternate theme or hardening file permissions to prevent PHP writes will reduce the RCE blast radius.

Affected VersionsENISA

Streamit 0 ≤4.5.0

Affected Packages

euvd streamit 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

Streamit is a premium video/streaming-oriented WordPress theme that registers AJAX handlers via WordPress's admin-ajax.php mechanism using the wp_ajax_nopriv_* hook, which exposes actions to unauthenticated visitors. This is a CWE-94 (Code Injection) flaw: one nopriv AJAX route accepts a PHP function name and an argument array from the request and dispatches them through a variable-function or call_user_func-style invocation without any capability check or nonce (CSRF token) validation. Because WordPress's function space includes primitives like wp_insert_user/wp_create_user and other side-effecting calls, arbitrary-function invocation with controlled arguments is effectively a code-execution and account-provisioning primitive.

Know when Streamit 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 (WPScan) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Unauthenticated network AJAX route (AV:N/PR:N/UI:N) with reliable arbitrary-function invocation (AC:L) yielding full code execution, so C/I/A all High.

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

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

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

Lifecycle Timeline

3
CVSS changed
Jul 29, 2026 - 13:22 NVD
9.8 (CRITICAL)
CVE Published
Jul 29, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 29, 2026 - 06:00 cve.org
CRITICAL 9.8

DescriptionCVE.org

The Streamit WordPress theme through 4.5.0 does not perform any authorization or nonce verification on one of its unauthenticated AJAX routes, which invokes an attacker-supplied PHP function with an attacker-supplied argument array, allowing unauthenticated attackers to call arbitrary functions (for example to create an administrator account), leading to privilege escalation and remote code execution.

Executive ViewAI

Why It Matters

The Streamit WordPress theme (versions up to 4.5.0) contains a critical unauthenticated remote code execution vulnerability allowing attackers to create administrator accounts and execute arbitrary code without authentication. All WordPress installations using this theme are immediately at risk of complete compromise. No vendor patch is currently available.

Business Impact: Severe
Compensating Controls

Disable or remove the Streamit theme; restrict WordPress access to specific IP ranges or internal networks only; implement Web Application Firewall rules blocking requests to the vulnerable AJAX endpoint; or isolate affected installations from production networks. These mitigations do not eliminate risk-full removal and migration to a currently maintained WordPress theme is the only effective remediation.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Low
niche commercial WordPress streaming theme, limited site footprint
Exploit
POC
Public exploit code exists
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 CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
CRITICAL severity + public POC available
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
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

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

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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