Skip to main content

ThemeRex Law Office EUVDEUVD-2026-96507

| CVE-2026-62120 CRITICAL
Deserialization of Untrusted Data (CWE-502)
2026-10-10 Patchstack GHSA-5mqj-g4vh-q3mp
9.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Reach WordPress site with vulnerable theme
  2. Delivery
    Send crafted serialized PHP object
  3. Exploit
    Trigger unsafe deserialization (CWE-502)
  4. Execution
    Instantiate POP gadget chain
  5. Impact
    Execute code or file operations on server

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

Exploitation requires a target WordPress installation running the ThemeRex 'Law Office' theme at version 3.20 or earlier; the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, no user interaction, and no special non-default configuration is needed beyond having the vulnerable theme active. The practical limiting factor for full code execution is the availability of a usable PHP object-injection gadget chain (POP chain) in the theme, loaded plugins, or WordPress core; without a reachable gadget the deserialization may yield lower impact than the 9.8 implies. Deployment is further limited to sites that have purchased and enabled this specific commercial legal-industry theme.

Impact

All provided signals point to a high-priority network-exploitable flaw: the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) describes remote, unauthenticated, low-complexity exploitation with no user interaction and full confidentiality/integrity/availability impact, which is consistent with CWE-502 (deserialization of untrusted data) leading to PHP Object Injection. The vulnerability class is well understood and, when a usable POP gadget chain exists in the theme or its bundled libraries, typically yields remote code execution. However, several key risk signals are MISSING from the input and must not be assumed: no EPSS score is provided, so exploitation probability cannot be quantified; KEV status is absent, so there is no evidence of active exploitation (treat as not KEV-listed); and no POC reference is present, so no public exploit is confirmed. There is also no SSVC decision data. The one contextual caveat is that CWE-502 PHP Object Injection often requires a reachable gadget chain to achieve full impact - the raw 9.8 assumes worst-case code execution, so real-world impact may vary depending on which libraries the theme loads. Net: credible high priority driven by the unauthenticated network vector, but with unknown real-world exploitation volume given absent EPSS/KEV/POC signals.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a crafted request to a WordPress site running the ThemeRex Law Office theme (<= 3.20) containing a malicious serialized PHP object, which is deserialized by vulnerable theme code. If a suitable property-oriented programming (gadget) chain is present in the theme, plugins, or WordPress core, the injected object triggers arbitrary code execution or file operations on the server. No public exploit code was identified in the provided data, so this scenario is based on the CVSS vector and the CWE-502 class rather than an observed exploit.

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

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

Alert me

AnalysisAIv1 – Oct 10, 2026

Unauthenticated PHP object injection in the ThemeRex 'Law Office' WordPress theme at version 3.20 and earlier lets remote attackers with no credentials and no user interaction pass attacker-controlled serialized data into an unsafe unserialize() path, which the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) scores as complete loss of confidentiality, integrity and availability. Practical impact depends heavily on whether a usable POP gadget chain exists in the theme, an installed plugin, or WordPress core; without a reachable gadget the result may be far below the theoretical 9.8 headline score. No CISA KEV entry, EPSS score, or public exploit code is present in the available intelligence, so this is assessed as no public exploit identified at time of analysis, and exposure is limited to sites running this commercial legal-industry theme.

RemediationAI

Available data does not identify a vendor-released patch or a fixed version number for this issue - the Patchstack advisory (https://patchstack.com/database/wordpress/theme/law-office/vulnerability/wordpress-law-office-theme-3-20-php-object-injection-vulnerability?_s_id=cve) and the ThemeRex vendor channel should be checked first for an updated theme release, and any version above 3.20 should be applied immediately once it exists. Because no fix version is confirmed, treat compensating controls as mandatory in the interim: the strongest option is to back up, then deactivate and uninstall the Law Office theme until a patched build is available, accepting the loss of the site's front-end presentation; if the theme must stay live, restrict the affected endpoints to trusted sources, block POST bodies containing PHP serialization signatures such as 'O:' followed by a class name and length prefix at the WAF or reverse proxy, and rate-limit or disable theme AJAX/REST handlers that are not required for the public site. Be aware that serialization-pattern WAF rules are bypassable via encoding, whitespace, and alternate formats, so they reduce rather than eliminate risk, and blocking broadly can break legitimate plugin traffic. Additionally, review installed plugins for usable gadget chains and keep WordPress core and all plugins current to shrink the POP-gadget surface, enable file-integrity monitoring and PHP error/dispatch logging to catch unexpected object instantiation, and consider disable_functions for high-risk PHP sinks such as exec, shell_exec and system, with the caveat that this may break legitimate theme features.

Affected VersionsENISA

Law Office n/a ≤3.20

Affected Packages

euvd law_office 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 root cause is CWE-502, deserialization of untrusted data, in a PHP/WordPress context. PHP object injection occurs when attacker-supplied input is passed to unserialize(), letting an attacker instantiate arbitrary classes and control their properties; the actual damage is triggered by magic methods such as __wakeup, __destruct, __toString and __call that execute during or after object reconstruction. Achieving code execution or file deletion requires a POP (property-oriented programming) gadget chain - a sequence of classes already loaded via the theme, its bundled plugins, or WordPress core whose magic methods chain into a dangerous sink such as file writes, call_user_func, or SQL. The CPE string cpe:2.3:a:themerex:law_office:*:*:*:*:*:*:*:* identifies the vendor as themerex and the product as law_office with an unbounded version wildcard, matching the described 'through 3.20' range; there is no platform or version granularity beyond the theme itself. The input's 'Microsoft' tag is not corroborated by the CPE, description, or advisory and appears to be misclassified metadata rather than an actual affected platform. The single reference is a Patchstack database entry for the WordPress theme, which is consistent with this being a theme-level WordPress component issue rather than a core or server-side flaw.

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 CWE-502 object injection reachable over the network with no user interaction (AV:N/AC:L/PR:N/UI:N); worst-case RCE justifies C:H/I:H/A:H, scope unchanged.

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 Law Office <= 3.20 versions.

Executive ViewAI

Why It Matters

The ThemeRex 'Law Office' WordPress theme (version 3.20 and earlier) contains a critical unauthenticated PHP object injection vulnerability that could allow remote attackers to fully compromise affected websites. Legal industry organizations running this theme face potential data breaches, site defacement, and operational disruption, which may lead to reputational harm and regulatory scrutiny. With no vendor patch available, immediate mitigation is required to protect sensitive client information and maintain trust.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: virtual patching via WAF to block serialized object injection attempts; temporarily deactivating the affected theme if feasible; restricting access to wp-admin and enforcing least privilege; monitoring web server and application logs for signs of exploitation; and applying security hardening such as disabling PHP unserialize() where possible or using a WordPress security plugin with object injection protection.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Prevalence
Low
niche commercial WordPress theme (ThemeRex Law Office), limited deployment footprint
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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
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
Out-of-Cycle
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