Skip to main content

Le Truffe CVE-2026-61998

| EUVDEUVD-2026-112964 CRITICAL
Deserialization of Untrusted Data (CWE-502)
2026-10-29 Patchstack GHSA-gwhg-6fhx-grcx
9.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Send crafted request with serialized PHP object
  2. Exploit
    Reach unserialize() in vulnerable theme
  3. Impact
    Instantiate gadget chain for RCE or data access

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, 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 target must be running the ThemeRex 'Le Truffe' WordPress theme at version 1.1.7 or earlier, with the vulnerable deserialization code path reachable by an unauthenticated network request (consistent with AV:N/PR:N/UI:N). The specific parameter, endpoint, or SAPI that reaches unserialize() is not described in the available sources. The principal limiting factor is that PHP object injection yields code execution or high-impact actions only when a suitable POP gadget chain exists in the loaded WordPress core, plugins, or theme code; without such a chain, impact may be reduced to a lesser effect. No authentication, non-default configuration, or user interaction is required according to the supplied vector.

Impact

Signals conflict in a way worth stating plainly. The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H → 9.8) and the vuln.today 'act_now' decision label both argue for urgent treatment: a network-reachable, unauthenticated flaw with no user interaction and full confidentiality/integrity/availability impact. CWE-502 (deserialization) in a WordPress theme is a well-understood, high-impact class. However, several corroborating risk signals are ABSENT rather than negative: no EPSS exploitation-probability score is provided, the CVE is NOT listed in CISA KEV, and no confirmed public exploit code is present - the single reference is a Patchstack advisory, not a weaponized PoC. The real-world footprint is also low: 'Le Truffe' is a niche ThemeRex WordPress theme, so even a CRITICAL rating translates to a small absolute attack surface. Net assessment: this is a genuinely severe vulnerability by mechanism and CVSS, and the 'act_now' label should be honored for anyone actually running the theme, but there is no evidence yet of widespread or active exploitation - treat it as high-priority patching for affected sites rather than an emergency fleet-wide incident. Note also that object-injection impact (C:H/I:H/A:H) is realized only when a usable POP gadget chain exists in the loaded WordPress/PHP code; the description does not confirm the trigger, so the maximal CVSS impact is an upper bound.

Exploit ScenarioDerived

A remote attacker sends a crafted request to a WordPress site running the Le Truffe theme (≤ 1.1.7) containing a serialized PHP object in an attacker-controlled parameter that reaches an unserialize() call. Because CVSS indicates no authentication and no user interaction (PR:N/UI:N) over the network (AV:N/AC:L), exploitation needs no login or victim action. Actual code execution or data compromise depends on a usable POP gadget chain being present; no confirmed public exploit code was identified at time of analysis - only a Patchstack advisory reference.

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

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

Alert me

AnalysisAIv1 – Oct 29, 2026

Signals conflict in a way worth stating plainly: the Le Truffe WordPress theme through version 1.1.7 contains an unauthenticated PHP object injection (CWE-502) scored CVSS 9.8, but whether it yields code execution or other high-impact actions depends on a suitable POP gadget chain in the loaded WordPress core, plugins, or theme code. Patchstack is the reporting source and the vuln.today decision label is act_now; no public exploit identified at time of analysis, and the vulnerable parameter and endpoint are not described in the supplied data.

RemediationAI

No vendor-released patch is identified in the available data, and no exact fixed version is listed; check the Patchstack advisory at https://patchstack.com/database/wordpress/theme/letruffe/vulnerability/wordpress-le-truffe-theme-1-1-7-php-object-injection-vulnerability?_s_id=cve for an updated release. If no fixed Le Truffe version is confirmed, the exposed code path can only be removed by disabling or removing the theme, which changes site appearance and may break templates that depend on it. Because the vulnerable parameter and endpoint are not described in the supplied evidence, targeted WAF or access-control rules cannot be specified from the available data.

Affected VersionsENISA

Le Truffe n/a ≤1.1.7

Affected Packages

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

The issue is a PHP object injection class flaw (CWE-502: Deserialization of Untrusted Data) in a WordPress theme. In PHP, object injection occurs when attacker-controlled input reaches a deserialization path such as unserialize(); the immediate effect is instantiation of attacker-influenced objects, and the impact escalates to code execution or other high-impact actions only when a usable POP gadget chain exists among the loaded WordPress core, plugin, or theme classes. The CPE cpe:2.3:a:themerex:le_truffe:*:*:*:*:*:*:*:* identifies ThemeRex's Le Truffe theme, and the advisory covers versions up to 1.1.7. The supplied sources do not state which parameter, endpoint, or server API reaches the vulnerable deserialization path.

Know when PHP 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.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Unauthenticated network-reachable object injection with no user interaction (AV:N/AC:L/PR:N/UI:N); a reachable gadget chain can yield full compromise, so C:H/I:H/A:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/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
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Unauthenticated PHP Object Injection in Le Truffe <= 1.1.7 versions.

Executive ViewAI

Why It Matters

The Le Truffe WordPress theme (versions through 1.1.7) contains a critical unauthenticated PHP object injection vulnerability (CVE-2026-61998, CVSS 9.8). This flaw allows remote attackers to potentially compromise the confidentiality, integrity, and availability of any WordPress site using the theme, with impact severity depending on the presence of a POP gadget chain in the site's plugins or core. Leadership should prioritize remediation because public exploit code may emerge and the theme is likely used on public-facing websites.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling or removing the theme, deploying a WAF with virtual patching, restricting access to vulnerable endpoints, and conducting a security review for POP gadget chains.

Threat Intelligence Overview

EPSS Score
0.5%
Top 59% exploitable
Prevalence
Low
niche ThemeRex WordPress theme, limited installed base
Data Quality
4 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.5%
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
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

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

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

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