Skip to main content

Stargaze WordPress Theme CVE-2026-62051

| EUVDEUVD-2026-96475 CRITICAL
Deserialization of Untrusted Data (CWE-502)
2026-10-10 Patchstack GHSA-2x62-wvm4-6vw5
9.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Identify site running Stargaze theme
  2. Delivery
    Send request with crafted serialized object
  3. Exploit
    Trigger unserialize() of attacker data
  4. Execution
    Invoke POP gadget chain
  5. Impact
    Achieve code execution or data compromise

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

Requires that the Stargaze WordPress theme version 1.10 or earlier is installed and active, and that the vulnerable code path passes attacker-controlled input to a PHP unserialize() call reachable without authentication. Per CVSS PR:N/UI:N, no login or user interaction is required and it works against default installations. The practical limiting factor is the need for a usable POP gadget chain (within the theme, a co-installed plugin, or WordPress core) for the object injection to produce meaningful impact such as code execution; without a suitable chain, impact may be reduced. Exploitation is further bounded to sites actually running this specific theme.

Impact

All signals point to a genuinely high-priority vulnerability, though exploitability depends on a factor the data cannot confirm. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes network-reachable, low-complexity, unauthenticated exploitation with full C:H/I:H/A:H impact (9.8 Critical), and CWE-502 deserialization flaws routinely escalate to remote code execution. However, PHP Object Injection is only directly weaponizable when a suitable POP (property-oriented programming) gadget chain is present in the theme or a co-installed plugin/WordPress core; the single Patchstack reference does not confirm whether such a chain ships with Stargaze, so the practical jump from injection to RCE is INFERRED, not confirmed. No EPSS score was provided in the input, so exploitation probability cannot be quantified. The vulnerability is NOT in CISA KEV and no public POC is referenced, so this is no public exploit identified at time of analysis - there is no evidence of active or widespread exploitation despite the critical score. Net: treat as a real patch-now priority for anyone running the Stargaze theme because of the unauthenticated network vector, but recognize the real-world footprint is small (niche WordPress theme) and the CVSS reflects worst-case object-injection potential rather than a demonstrated exploit.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a crafted request to a WordPress site running the Stargaze theme (<= 1.10) containing a malicious serialized PHP object in a parameter that the theme passes to unserialize(). If a usable gadget chain exists in the theme, an installed plugin, or WordPress core, the injected object triggers unintended method calls that can lead to file operations, SQL interaction, or arbitrary code execution. No public exploit code is referenced, so an attacker would need to identify a working POP chain for the target environment.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.4% 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 Stargaze WordPress theme (versions 1.10 and earlier) allows remote attackers to submit a crafted serialized payload that the theme feeds to PHP's unserialize(), which can trigger arbitrary object instantiation and, where a usable gadget chain is present, code execution or full site compromise; the maximum-base CVSS 3.1 score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects high confidentiality, integrity, and availability impact. Per that vector no authentication (PR:N) and no user interaction (UI:N) are required, and the CPE record cpe:2.3:a:themerex:stargaze ties the exposure to the ThemeREX Stargaze theme, so only sites with this theme installed and active are in scope. At time of analysis there is no public exploit identified, and the practical ceiling on impact depends on whether a viable POP gadget chain exists in the theme itself, a co-installed plugin, or WordPress core.

RemediationAI

No vendor-released patch identified at time of analysis, and no fixed version is specified in the available data, so the primary action is to deactivate and remove the Stargaze theme from any production site and migrate to a currently maintained theme - the trade-off is an immediate change to site appearance and potentially to theme-dependent functionality, which should be staged on a copy first. If removal cannot be done immediately, deploy virtual patching at the WAF or security-plugin layer that blocks request parameters and bodies containing PHP serialized-object patterns (for example payloads beginning with O: followed by a length and class name, or C: for Serializable); be aware such rules can produce false positives against legitimate plugin data and must be tuned and monitored. In parallel, shrink the available gadget surface by updating WordPress core and every installed plugin to their latest releases, deleting plugins and themes that are inactive or abandoned, and restricting the site so only required plugins load on public-facing requests. Continue to monitor the Patchstack advisory at https://patchstack.com/database/wordpress/theme/stargaze/vulnerability/wordpress-stargaze-theme-1-10-php-object-injection-vulnerability?_s_id=cve for a vendor fix, and treat any newly published Stargaze release as the signal to patch and re-enable the theme rather than assuming the current exposure is permanent.

Affected VersionsENISA

Stargaze n/a ≤1.10

Affected Packages

euvd stargaze 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 class is CWE-502 (Deserialization of Untrusted Data) in PHP, where attacker-controlled input reaches unserialize() without authentication. PHP deserialization does not merely reconstruct data: it instantiates classes and invokes magic methods such as __wakeup, __destruct, and __toString, so an attacker who controls the serialized string can steer object construction into the code paths of already-loaded classes. Real-world impact from this flaw class almost always rides on a POP (property-oriented programming) gadget chain - a sequence of magic methods in the theme, an installed plugin, or WordPress core that converts object instantiation into file writes, file inclusion, SQL execution, or command execution; without such a chain the result is typically limited to object injection side effects. The affected component is a WordPress theme distributed by ThemeREX, and the CPE cpe:2.3:a:themerex:stargaze identifies it as the target product, with the advisory specifying versions up to and including 1.10. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N with scope unchanged (S:U), the vulnerable entry point is reachable over the network from an unauthenticated client against a default installation, which in WordPress themes generally means an endpoint, action hook, or REST/AJAX path that processes request data before any capability check - a common anti-pattern because PHP offers no mechanism to safely deserialize data from untrusted sources, and the only reliable fix is to avoid unserialize() on user input in favor of JSON or another non-executable format.

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 (PR:N) network-reachable (AV:N) deserialization with no user interaction; object injection can yield full C/I/A impact, so AC:L and H/H/H retained.

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 Stargaze <= 1.10 versions.

Executive ViewAI

Why It Matters

The ThemeREX Stargaze WordPress theme (versions 1.10 and earlier) contains a critical unauthenticated PHP object injection vulnerability that could allow remote attackers to achieve full site compromise, impacting confidentiality, integrity, and availability. With no vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, the risk remains severe for organizations using this theme, as successful exploitation could lead to data breaches, website defacement, and operational disruption.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include deactivating or removing the vulnerable Stargaze theme until a fix is released; if the theme must remain active, deploy a Web Application Firewall (WAF) with virtual patching rules to detect and block PHP object injection attempts (e.g., blocking serialized payloads in HTTP requests), restrict access to the WordPress admin interface, enable robust logging and monitoring for indicators of compromise, ensure frequent backups are stored offline, and consider using a security plugin that offers virtual patching for this CVE.

Threat Intelligence Overview

EPSS Score
0.4%
Top 69% exploitable
Prevalence
Low
niche ThemeRex WordPress theme, limited installation base
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.4%
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