What is the CVSS score of EUVD-2026-41332?

EUVD-2026-41332 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of Werkstatt are affected by EUVD-2026-41332?

The Werkstatt WordPress theme (fuelthemes) through version 4.8.3 contains a critical PHP object injection vulnerability (CVSS 8.8) that allows Contributor-level users to trigger unsafe…

How to fix or mitigate EUVD-2026-41332?

24 hours: Scan all WordPress installations for Werkstatt theme usage through version 4.8.3; immediately deactivate the theme or restrict Contributor user permissions to essential personnel. 7 days: Review contributor account activity logs for exploitation attempts; deploy enhanced logging for deserialization operations. 30 days: Complete migration to alternative WordPress theme; implement organization-wide restrictions on contributor role creation.

Werkstatt EUVD-2026-41332

| CVE-2026-27414 HIGH

Deserialization of Untrusted Data (CWE-502)

2026-07-02 Patchstack

GHSA-3236-q4rc-wfw4

PHP WordPress Deserialization Werkstatt Wordpress Theme Fuelthemes

8.8

CVSS 3.1 · Vendor: Patchstack

Severity by source

Vendor (Patchstack) PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

8.8 HIGH

Remote, low-complexity object injection reachable by a Contributor (PR:L), no user interaction, with gadget-chain-driven high C/I/A impact within the same WordPress instance (S:U).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 02, 2026 - 12:10 vuln.today

DescriptionCVE.org

Contributor PHP Object Injection in Werkstatt <= 4.8.3 versions.

AnalysisAI

PHP Object Injection in the Werkstatt WordPress theme (fuelthemes) through version 4.8.3 lets a Contributor-level user pass attacker-controlled data into an unsafe deserialization routine, enabling instantiation of arbitrary PHP objects. With the right POP gadget chain present in WordPress core, another plugin, or the theme itself, this can escalate to file operations, SQL manipulation, or remote code execution. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the 8.8 CVSS reflects the low-privilege network-exploitable path with high confidentiality, integrity, and availability impact.

Technical ContextAI

The affected component is the Werkstatt commercial WordPress theme distributed by fuelthemes, identified by CPE cpe:2.3:a:fuelthemes:werkstatt (all versions up to and including 4.8.3). The root cause is CWE-502, Deserialization of Untrusted Data: PHP's unserialize() (or an equivalent) is invoked on input a Contributor can influence, causing PHP to reconstruct objects whose magic methods (__wakeup, __destruct, __toString) fire automatically. PHP Object Injection itself does not execute code directly - it becomes dangerous when a 'property-oriented programming' (POP) gadget chain exists in the loaded codebase (WordPress core, active plugins, or the theme), which the attacker's crafted serialized payload steers toward a sensitive sink. This is a well-understood WordPress theme/plugin vulnerability class routinely triaged by Patchstack.

RemediationAI

No specific fixed version was provided in the source data, so the patch status is: no vendor-released patch version identified at time of analysis - check the Patchstack advisory (https://patchstack.com/database/wordpress/theme/werkstatt/vulnerability/wordpress-werkstatt-theme-4-8-3-php-object-injection-vulnerability) and the fuelthemes/ThemeForest changelog for a release above 4.8.3 and upgrade to it as the primary fix. Until a patched release is confirmed, reduce risk by removing the Contributor role from untrusted users and disabling open user registration (side effect: legitimate multi-author workflows are curtailed), auditing and removing unused plugins that could supply POP gadget chains (side effect: possible loss of dependent functionality), and deploying a WAF or Patchstack virtual patch to block serialized-object payloads in requests reaching the theme (side effect: potential false positives on legitimate serialized data). Where feasible, restrict access to the theme's affected endpoint/handler to authenticated administrators only.