LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22454: WordPress Solaris theme <= 2.5 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in ThemeREX Solaris solaris allows Object Injection.This issue affects Solaris: from n/a through <= 2.5.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-22454 is a critical vulnerability in the WordPress Solaris theme from ThemeREX, affecting versions through 2.5. It involves unsafe handling of serialized data and could allow PHP object injection. The public record rates potential impact as complete confidentiality, integrity, and availability compromise. No cited source confirms active exploitation.

Executive priority

Prioritize within the next remediation cycle, sooner for public or revenue-impacting WordPress sites. The score is critical and unauthenticated network exploitation is indicated by CVSS, but public evidence of active exploitation or a specific patch is not present in the supplied sources.

Technical view

The issue is CWE-502, deserialization of untrusted data, in ThemeREX Solaris WordPress theme <= 2.5. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. Public sources do not provide vulnerable endpoint details, proof-of-concept status, or a confirmed fixed version.

Likely exposure

Exposure is likely limited to WordPress sites with the Solaris theme installed at version 2.5 or earlier. Internet-facing WordPress deployments are higher priority because the CVSS vector indicates network reachability without authentication.

Exploitation context

The CVE record and Patchstack entry indicate PHP object injection risk, but the provided sources do not confirm exploitation in the wild. The CVE is not listed as KEV in the supplied data. Treat as high urgency because exploitation requires no privileges or user interaction per CVSS.

Researcher notes

Evidence is sparse. The public data identifies CWE-502 in Solaris <= 2.5 and a 9.8 CVSS vector. It does not include exploit mechanics, affected code paths, PoC, or fixed-version metadata. Validate exposure by installed theme version and track vendor/Patchstack updates.

Mitigation direction

  • Identify WordPress sites using the ThemeREX Solaris theme.
  • Check whether installed Solaris versions are 2.5 or earlier.
  • Review ThemeREX and Patchstack guidance for a fixed version or workaround.
  • Remove or replace the theme if it is unused or cannot be safely maintained.
  • Prioritize remediation on internet-facing and business-critical WordPress sites.

Validation and detection

  • Inventory WordPress themes across production, staging, and backup sites.
  • Confirm Solaris theme version from trusted administrative or asset records.
  • Check vendor and Patchstack pages for updated remediation information.
  • Review web and application logs for unusual requests around affected sites.
  • Document compensating controls if immediate removal or update is not possible.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22454 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-22454Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeREXSolarissolaris, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.