Skip to main content

Webriti Wallstreet EUVDEUVD-2026-91774

| CVE-2026-39718 HIGH
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-10-02 Patchstack GHSA-p2px-q24r-qwp5
8.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Lure authenticated admin to malicious page
  2. Exploit
    Browser auto-submits forged theme request
  3. Execution
    Missing CSRF nonce check bypassed
  4. Impact
    Unauthorized state change applied

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

Exploitation requires a victim who is authenticated to the WordPress site (realistically an administrator) and who is tricked into visiting attacker-controlled content or clicking a malicious link while that session is active - this user-interaction requirement (UI:R) is the primary limiting factor. The underlying prerequisite is that the Wallstreet theme (versions n/a through 2.8.6) performs a state-changing operation without validating an anti-CSRF nonce. The attacker needs no credentials or prior access, but cannot succeed against an administrator who is not logged in or who does not interact with the forged request; sites running a patched version above 2.8.6 (version unspecified in input) are not affected.

Impact

This is a CWE-352 Cross-Site Request Forgery in the Webriti 'Wallstreet' WordPress theme (versions up to and including 2.8.6), reported by Patchstack with an assigned CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The vector indicates a network-reachable, low-complexity attack needing no attacker privileges but requiring user interaction (UI:R) - characteristic of CSRF, where the request is forged but must be triggered by a logged-in victim (typically an authenticated administrator) visiting an attacker-controlled page. No EPSS score, CISA KEV listing, or public proof-of-concept was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The headline 8.8 score is driven by the triple-High C/I/A impact Patchstack assigns, but CSRF realistically yields only the state-changing action the forged request performs and is gated by the UI:R requirement and by the victim needing an active authenticated session - so the practical priority is lower than the 8.8 suggests. Note the tension: PR:N labels the attack 'unauthenticated' (true for the attacker), yet successful exploitation depends entirely on an authenticated administrator being tricked into triggering the request - verify the actual sensitivity of the affected action with the Patchstack advisory before treating this as critical.

Exploit ScenarioDerived

An attacker crafts a malicious web page or email containing a forged request targeting a privileged Wallstreet theme action and lures a logged-in WordPress administrator into visiting it. Because the theme does not validate a CSRF nonce, the victim's browser submits the state-changing request using their active session. No public proof-of-concept was provided, and exploitation requires the victim to be authenticated and to interact with the attacker's content (UI:R).

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

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

Alert me

AnalysisAIv1 – Oct 02, 2026

Cross-site request forgery in the Webriti 'Wallstreet' WordPress theme affects all versions through 2.8.6, letting an attacker forge state-changing requests that are executed with the privileges of a logged-in site administrator. The independent assessment rates this at CVSS 3.1 4.3-class impact (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) rather than the vendor-published 8.8, because exploitation depends on tricking an already-authenticated admin into visiting attacker-controlled content or clicking a crafted link while their session is active - the UI:R requirement is the primary limiting factor. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the advisory (reported by Patchstack) indicates versions above 2.8.6 are not affected, though the input does not name that fixed version.

RemediationAI

No vendor-released patch with a confirmed version number was identified in the provided data; the advisory indicates the issue affects Wallstreet through 2.8.6 and implies a corrected release above that version, but the exact fixed version is not specified, so treat that as 'Upstream fix implied; released patched version not independently confirmed' and verify the latest release on the vendor/WordPress.org theme page before upgrading. Until a patched build is installed, apply compensating controls: keep administrator sessions short and log out when not actively administering the site (the attack cannot succeed without a live authenticated session); avoid browsing untrusted or attacker-supplied links in the same browser profile used for wp-admin, which removes the delivery vector at the cost of workflow convenience; enforce SameSite=Lax or Strict on WordPress authentication cookies so cross-site forged requests do not carry the admin cookie (this can break legitimate cross-site integrations and some SSO flows); and deploy a WAF or WordPress security plugin rule set that blocks cross-site state-changing requests to the theme's admin-ajax/admin-post endpoints, accepting that such rules may produce false positives on legitimate admin traffic. None of these substitutes for upgrading once the patched version is available; the Patchstack entry at https://patchstack.com/database/wordpress/theme/wallstreet/vulnerability/wordpress-wallstreet-theme-2-8-6-cross-site-request-forgery-csrf-vulnerability?_s_id=cve is the reference to monitor for the fix version.

Affected VersionsENISA

Wallstreet 0 ≤2.8.6

Affected Packages

euvd wallstreet 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 (Cross-Site Request Forgery) in a WordPress theme is a classic missing-token class of bug: the Wallstreet theme processes a state-changing action without validating a WordPress anti-CSRF nonce (the wp_nonce_field()/check_admin_referer() mechanism), so the browser's ambient authentication cookies are sufficient to authorize the forged request. Because the request originates from the victim's browser with their session, the server cannot distinguish it from a legitimate admin action. The CPE cpe:2.3:a:webriti:wallstreet:*:*:*:*:*:*:*:* confirms the affected product is the theme package itself with all versions matched, and the reference points to the Patchstack WordPress theme vulnerability database entry for version 2.8.6. The classic delivery path is a malicious page, email link, or third-party site the admin visits while logged in; same-site cookie policy and nonce validation are the standard defenses. Note the divergence between the vendor-published CVSS vector (C:H/I:H/A:H) and the independent vector (C:L/I:L/A:N), which treats the practical impact of a forged request as limited rather than full site compromise.

Know when Wallstreet 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
vuln.today AI 5.4 MEDIUM

Network CSRF needs no attacker privileges (PR:N) but requires a logged-in victim to interact (UI:R); absent detail on the abused action, impact is assessed as limited integrity/confidentiality rather than Patchstack's triple-High.

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

Primary rating from Vendor (Patchstack).

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 Webriti Wallstreet wallstreet allows Cross Site Request Forgery.This issue affects Wallstreet: from n/a through 2.8.6.

Executive ViewAI

Why It Matters

The Webriti 'Wallstreet' WordPress theme (versions through 2.8.6) contains a cross-site request forgery vulnerability that could allow an attacker to perform administrative actions on behalf of a logged-in site administrator; no public exploit identified at time of analysis. Organizational impact is limited to sites using this theme, where unauthorized changes to content or configuration could occur if an administrator is tricked into clicking a crafted link while authenticated; No vendor-released patch identified at time of analysis. Leadership should care because affected WordPress properties require temporary mitigations until a fixed version above 2.8.6 is confirmed and deployed.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis; disable or remove the Webriti 'Wallstreet' theme, restrict wp-admin access by IP, enforce multi-factor authentication, deploy WAF rules to block CSRF attempts, and log out of admin sessions after use.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
niche third-party WordPress theme, limited deployment footprint
Data Quality
6 sources
Confidence: High

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.1%
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
Medium
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