Skip to main content

Theme Editor CVE-2026-39640

| EUVDEUVD-2026-20300 CRITICAL
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-04-08 Patchstack GHSA-hgvj-3389-4m2h
9.6
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Recon
    Identify target site with Theme Editor ≤3.2
  2. Delivery
    Craft CSRF payload with PHP backdoor injection
  3. Exploit
    Social engineer admin to visit attacker page
  4. Install
    Admin browser auto-submits CSRF request
  5. C2
    Malicious code injected into theme files
  6. Execute
    Backdoor executes with web server privileges
  7. Impact
    Complete site compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

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

Exploitation Conditions

The victim must be logged into WordPress with Theme Editor plugin (version ≤3.2) and click a link or visit a page crafted by the attacker. Attacker is an unauthenticated remote user.

Impact

Despite the critical CVSS base score of 9.6, real-world exploitation risk is moderate. The CVSS vector reveals required user interaction (UI:R) as a key barrier-an authenticated administrator must be social-engineered into triggering the malicious request. The EPSS score of 0.01% (1st percentile) indicates researchers and attackers currently assess this as low probability for widespread exploitation, likely due to the targeting precision required (must reach WordPress admins of sites running this specific plugin). No public exploit identified at time of analysis and no CISA KEV listing confirms this is not being actively exploited at scale. However, the scope change (S:C) and complete confidentiality/integrity/availability impact (C:H/I:H/A:H) mean successful exploitation results in full site compromise and potential server takeover. The no-privileges-required rating (PR:N) is technically accurate-the HTTP request itself is unauthenticated-but misleading without context: the victim admin must already be authenticated to WordPress when the CSRF payload executes. This is a high-severity issue for sites using Theme Editor 3.2 or earlier, but requires targeted attack effort rather than opportunistic mass exploitation.

Exploit ScenarioDerived

An attacker identifies a WordPress site running Theme Editor 3.2, then crafts a malicious webpage containing hidden forms that POST code injection payloads to the plugin's unprotected theme editing endpoints. The attacker sends a phishing email to the site administrator with a pretext to visit the malicious page while logged into WordPress. When the admin visits, their browser automatically submits the CSRF payload, injecting PHP backdoor code into the active theme's functions.php file, granting the attacker persistent remote code execution and full control over the WordPress installation and underlying server.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.0% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Apr 14, 2026

Cross-Site Request Forgery in WordPress Theme Editor plugin versions through 3.2 enables unauthenticated attackers to inject arbitrary code via social engineering, achieving remote code execution with critical scope change impact. The vulnerability requires user interaction but no authentication (CVSS PR:N/UI:R), creating a pathway from CSRF to complete site compromise. EPSS exploitation probability is low (0.01%, 1st percentile), and no public exploit identified at time of analysis.

RemediationAI

Upgrade the Theme Editor plugin to a version newer than 3.2 if available from the WordPress plugin repository or vendor advisory at https://patchstack.com/database/Wordpress/Plugin/theme-editor/vulnerability/wordpress-theme-editor-plugin-3-2-cross-site-request-forgery-csrf-to-remote-code-execution-vulnerability. If no patched version exists or the plugin is no longer maintained, immediately disable and remove the Theme Editor plugin, as WordPress core includes built-in theme editing functionality for administrators (though disabling via DISALLOW_FILE_EDIT constant is recommended for production sites). As an interim mitigation if removal is not immediately feasible, implement web application firewall rules to block suspicious POST requests to theme editor endpoints, restrict WordPress admin access to trusted IP addresses, and educate administrators about CSRF risks including not clicking unknown links while logged into WordPress dashboards. Consult https://nvd.nist.gov/vuln/detail/CVE-2026-39640 for additional vendor guidance.

Affected VersionsENISA

Theme Editor 0 ≤3.2

Affected Packages

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

This vulnerability affects the Theme Editor WordPress plugin (cpe:2.3:a:mndpsingh287:theme_editor) through version 3.2. The root cause is CWE-352 (Cross-Site Request Forgery), where the plugin fails to implement proper anti-CSRF tokens or nonce validation on sensitive code modification endpoints. WordPress theme editors typically allow administrators to directly edit PHP template files, CSS, and JavaScript. Without CSRF protection, an attacker can craft malicious requests that, when executed by an authenticated administrator's browser, inject arbitrary PHP code into theme files. The CVSS scope change (S:C) indicates the vulnerability allows breaking out of the WordPress security context, as injected code executes with full web server privileges. The network attack vector (AV:N) combined with low complexity (AC:L) means exploitation requires only tricking an admin into visiting a malicious page while authenticated to WordPress.

Know when Theme Editor 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 9.6 CRITICAL
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Primary rating from Vendor (Patchstack) · only source for this CVE.

CVSS VectorVendor: Patchstack

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

Lifecycle Timeline

2
CVSS changed
Apr 14, 2026 - 15:22 NVD
9.6 (CRITICAL)
CVE Published
Apr 08, 2026 - 08:30 nvd
N/A

DescriptionCVE.org

Cross-Site Request Forgery (CSRF) vulnerability in mndpsingh287 Theme Editor theme-editor allows Code Injection.This issue affects Theme Editor: from n/a through <= 3.2.

Executive ViewAI

Why It Matters

CVE-2026-39640 is a critical cross-site request forgery vulnerability in WordPress Theme Editor plugin (versions ≤3.2) that allows unauthenticated attackers to inject arbitrary code and achieve remote code execution if a site administrator clicks a malicious link. This vulnerability threatens complete WordPress site compromise and requires immediate action despite low current exploitation probability.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: uninstall the vulnerable plugin; restrict administrative dashboard access by IP address; implement CSRF token validation at WAF layer; disable direct theme editing and enforce all changes through version-controlled code deployment; conduct phishing awareness training for WordPress administrators on CSRF attacks; monitor WordPress admin logs for unauthorized code injection attempts.

Threat Intelligence Overview

EPSS Score
0.0%
Top 99% exploitable
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 No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
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
Very High
Technical Impact
Total

Priority Score

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

Attack Technique

Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.

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