Skip to main content

Spicepress EUVDEUVD-2026-20263

| CVE-2026-39621 HIGH
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-04-08 Patchstack GHSA-pgqw-m834-qpv3
8.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Craft malicious webpage with CSRF payload
  2. Exploit
    Trick admin into visiting page
  3. Execution
    Submit unauthorized file upload request
  4. Impact
    Execute web shell on server

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 SpicePress <= 2.3.2.5 and click a link or visit a page crafted by the attacker. Remote unauthenticated attacker performs CSRF to upload web shell via authenticated user's session.

Impact

CVSS 8.8 reflects high impact (confidentiality, integrity, availability), but exploitation requires user interaction (UI:R) and unauthenticated network access. EPSS 0.01% indicates low observed exploitation activity. Real-world risk depends on SpicePress adoption and admin user targets; web shell upload would enable full site compromise if successful.

Exploit ScenarioDerived

Attacker crafts malicious link/form embedding CSRF payload targeting authenticated admin. Admin clicks link while logged into SpicePress dashboard; CSRF triggers unauthenticated file upload installing web shell. No public exploit code identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
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 08, 2026

CSRF vulnerability in SpicePress WordPress theme versions ≤2.3.2.5 enables unauthenticated attackers to upload web shells via arbitrary plugin installation, achieving remote code execution. Successful exploitation requires user interaction (victim must click malicious link while authenticated). No public exploit identified at time of analysis. CVSS 8.8 score reflects network-accessible, low-complexity attack with high impact to confidentiality, integrity, and availability.

RemediationAI

No vendor-released patch identified at time of analysis for SpicePress 2.3.2.5. Recommended immediate actions: (1) Deactivate SpicePress theme and migrate to actively maintained alternative WordPress theme; (2) Audit installed plugins for unauthorized additions; (3) Implement Web Application Firewall rules blocking unauthorized plugin uploads; (4) Monitor Patchstack advisory for vendor update: https://patchstack.com/database/Wordpress/Theme/spicepress/vulnerability/wordpress-spicepress-theme-2-3-2-5-csrf-to-arbitrary-plugin-installation-vulnerability?_s_id=cve. Workaround: Restrict WordPress admin access to trusted IP ranges via .htaccess or firewall ACLs. EPSS 0.01% indicates low observed exploitation activity.

Affected VersionsENISA

SpicePress 0 ≤2.3.2.5

Affected Packages

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

CWE-352 CSRF flaw permits state-changing operations without request verification tokens. Attack chain leverages missing anti-CSRF protections in theme's plugin installation mechanism, allowing HTTP request forgery to install malicious plugins containing web shells. cpe:2.3:a:spicethemes:spicepress references WordPress theme component vulnerable through upload functionality.

Know when Spicepress 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 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Cross-Site Request Forgery (CSRF) vulnerability in spicethemes SpicePress spicepress allows Upload a Web Shell to a Web Server.This issue affects SpicePress: from n/a through <= 2.3.2.5.

Executive ViewAI

Why It Matters

CVE-2026-39621 is a critical CSRF vulnerability in SpicePress WordPress theme (versions ≤2.3.2.5) that allows unauthenticated attackers to trick authenticated administrators into installing malicious plugins, resulting in remote code execution and complete system compromise. Organizations using this theme face immediate risk of data breach, website defacement, and infrastructure takeover if administrators are socially engineered into clicking malicious links.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Implement CSRF token validation at the web application firewall level for WordPress admin endpoints; (2) Restrict plugin installation permissions to only essential administrator accounts; (3) Require multi-factor authentication for all WordPress administrative accounts; (4) Deploy Content Security Policy (CSP) headers to block malicious cross-site requests; (5) Monitor WordPress plugin installation logs and audit trails for unauthorized activity; (6) Consider temporary deactivation of the SpicePress theme and use a hardened alternative.

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 HIGH
CISA KEV No
Public POC No
EPSS 0.0%
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
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
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