LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22500: WordPress m2 | Construction and Tools Store theme <= 1.1.2 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in axiomthemes m2 | Construction and Tools Store m2-ce allows Object Injection.This issue affects m2 | Construction and Tools Store: from n/a through <= 1.1.2.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-22500 is a critical vulnerability in the WordPress m2 | Construction and Tools Store theme. A remote attacker may be able to inject PHP objects through unsafe deserialization. The published score is 9.8, indicating potential full confidentiality, integrity, and availability impact. No provided source confirms active exploitation.

Executive priority

Treat as urgent for any public WordPress site using this theme. The vulnerability is rated critical and requires no authentication or user interaction. If the theme is absent, business risk from this CVE is not indicated by the provided sources.

Technical view

The issue is CWE-502, Deserialization of Untrusted Data, affecting axiomthemes m2 | Construction and Tools Store theme package m2-ce through version 1.1.2. The CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning network-reachable, unauthenticated, low-complexity exploitation with no user interaction.

Likely exposure

Exposure is limited to WordPress installations using the m2 | Construction and Tools Store theme, m2-ce, through version 1.1.2. Internet-facing WordPress sites using this theme should be prioritized because the CVSS vector indicates unauthenticated network access.

Exploitation context

The sources describe PHP object injection from unsafe deserialization but do not provide exploit details. CISA KEV status is false in the provided bundle, and no cited source confirms exploitation in the wild.

Researcher notes

The record names the affected product and class but does not include a fixed version, exploit chain, or proof of exploitation. Avoid assuming gadget availability or remote code execution without additional evidence from vendor or researcher publications.

Mitigation direction

  • Inventory WordPress sites for the m2-ce theme and its installed version.
  • Check the vendor and Patchstack entry for a fixed version or official mitigation.
  • Disable or remove the theme where it is not business-critical.
  • Prioritize compensating controls for internet-facing affected sites until vendor guidance is applied.
  • Back up sites before making theme or production changes.

Validation and detection

  • Confirm whether m2 | Construction and Tools Store theme is installed.
  • Verify whether the installed theme version is 1.1.2 or earlier.
  • Review vendor and Patchstack advisories for current remediation status.
  • Check web application logs for unusual requests targeting theme functionality.
  • Document affected sites, owners, exposure, and remediation status.
Prepared
Confidence
high
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-22500 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-22500Attack 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
axiomthemesm2 | Construction and Tools Storem2-ce, 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.