LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27437: WordPress Tennis Club theme <= 1.2.3 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in ThemeREX Tennis Club tennis-sportclub allows Object Injection.This issue affects Tennis Club: from n/a through <= 1.2.3.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-27437 is a critical vulnerability in the ThemeREX Tennis Club WordPress theme through version 1.2.3. A remote, unauthenticated attacker may be able to abuse unsafe data deserialization. The published scoring indicates potential full confidentiality, integrity, and availability impact, but public details are limited.

Executive priority

Treat as urgent for any public WordPress site using this theme. Confirm exposure quickly and remediate or remove the theme if affected. Do not assume exploitation is occurring without evidence, but the potential business impact is severe.

Technical view

The issue is CWE-502 deserialization of untrusted data leading to PHP object injection in the tennis-sportclub theme. CVSS 3.1 is 9.8: network attack vector, low complexity, no privileges, no user interaction. Exploitability and impact may depend on reachable vulnerable code paths and available PHP gadget chains.

Likely exposure

Internet-facing WordPress sites using ThemeREX Tennis Club / tennis-sportclub version 1.2.3 or earlier are the likely exposure group. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public exploit mechanics are not provided here. The risk remains high because the CVSS vector describes unauthenticated remote exploitation with severe potential impact.

Researcher notes

Public data identifies the bug class and affected theme range but does not include vulnerable endpoint details, proof-of-concept status, or a confirmed fixed version in the provided bundle. Object injection impact should be assessed in context of installed code and available classes.

Mitigation direction

  • Inventory WordPress sites for the Tennis Club / tennis-sportclub theme and version.
  • If affected, check ThemeREX and Patchstack guidance for an official fixed version or workaround.
  • Update the theme if a vendor-supported patched release is available.
  • If no fix is available, disable or remove the theme where business impact allows.
  • Prioritize externally reachable WordPress sites before internal or non-production instances.

Validation and detection

  • Confirm whether the theme directory or asset metadata identifies Tennis Club / tennis-sportclub.
  • Verify installed theme version and compare against version 1.2.3 or earlier.
  • Check whether the site is externally reachable and publicly indexed.
  • Review vendor and Patchstack advisories for updated affected-version and remediation details.
  • Monitor web logs and security tooling for anomalous unauthenticated requests to theme endpoints.
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-27437 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-27437Attack 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
ThemeREXTennis Clubtennis-sportclub, 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.