Skip to main content

Grand Portfolio CVE-2026-39634

| EUVDEUVD-2026-20289 MEDIUM
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-04-08 Patchstack
5.4
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Send crafted cross-site request
  2. Delivery
    Target authenticated admin session
  3. Exploit
    Bypass missing CSRF token validation
  4. Execution
    Modify theme settings or content
  5. Impact
    Impact site integrity or availability

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.

Impact

While the CVSS score of 5.4 suggests medium severity, multiple signals indicate low real-world risk. The EPSS score of 0.01% (bottom percentile) shows exploitation is exceptionally rare in observed data. The attack requires user interaction (UI:R) and network access (AV:N), meaning a victim must visit a malicious site while logged into their WordPress admin panel. The impact scope is unchanged (S:U), limiting effects to the vulnerable application only. Integrity and availability impacts are low (I:L, A:L)-not confidentiality compromise. For WordPress theme CSRF vulnerabilities targeting low-privilege content changes, this represents a lower practical risk than the CVSS suggests, particularly if the theme is not widely deployed or if administrators follow security hygiene practices. However, any unauthenticated CSRF remains a valid security concern in defense-in-depth strategies.

Exploit ScenarioDerived

An attacker creates a malicious website or sends a crafted HTML email containing an embedded request (e.g., an img tag or form submission) targeting the Grand Portfolio theme's admin settings endpoint. When an authenticated WordPress administrator visits the attacker's site while logged into their own WordPress dashboard, the browser automatically includes the admin's session cookies with the malicious request. Because the theme lacks CSRF token validation, the request succeeds, allowing the attacker to modify theme settings, inject malicious code into theme options, or alter published content without the admin's explicit consent. The attack is silent and requires no additional user interaction beyond visiting the malicious page.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.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 14, 2026

Cross-Site Request Forgery (CSRF) in ThemeGoods Grand Portfolio WordPress theme versions up to 3.3 allows unauthenticated remote attackers to perform unauthorized actions on behalf of authenticated users with low integrity and availability impact. The vulnerability requires user interaction (UI:R) to trigger a malicious request. No public exploit code or active exploitation has been confirmed, and the EPSS score of 0.01% indicates minimal real-world exploitation likelihood despite the CVSS 5.4 rating.

RemediationAI

Upgrade ThemeGoods Grand Portfolio to a version later than 3.3; the vendor advisory from Patchstack should confirm the exact patched version number. If upgrading is not immediately feasible, implement WordPress-level CSRF protections by ensuring all form submissions include valid WordPress nonces (wp_nonce_field() in forms and wp_verify_nonce() in handlers), and restrict administrative actions to logged-in users with appropriate capabilities. Review the theme's codebase in functions.php and relevant template files to identify forms lacking nonce validation, then add nonces to all state-changing requests. For WordPress administrators, enforce strong admin passwords, use two-factor authentication plugins, and monitor admin activity logs for suspicious changes. Refer to the Patchstack advisory at https://patchstack.com/database/Wordpress/Theme/grandportfolio/ for vendor-specific guidance.

Affected VersionsENISA

Grand Portfolio 0 ≤3.3

Affected Packages

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

Grand Portfolio is a WordPress theme distributed via the WordPress.org theme repository. CSRF vulnerabilities (CWE-352) occur when an application fails to implement anti-CSRF tokens (such as nonces in WordPress) or validate the origin of requests. The theme's lack of proper CSRF protection mechanisms allows attackers to craft malicious web pages or requests that, when visited by an authenticated admin or user, can trigger unintended actions-such as theme settings modifications or content changes-without the user's knowledge. The vulnerability affects all versions from the initial release through version 3.3, indicating the protection was either never implemented or introduced after 3.3.

Know when Grand Portfolio 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 5.4 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

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
None
Integrity
Low
Availability
Low

Lifecycle Timeline

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

DescriptionCVE.org

Cross-Site Request Forgery (CSRF) vulnerability in ThemeGoods Grand Portfolio grandportfolio allows Cross Site Request Forgery.This issue affects Grand Portfolio: from n/a through <= 3.3.

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

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