LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0677: WordPress TotalContest Lite plugin <= 2.9.1 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in TotalSuite TotalContest Lite totalcontest-lite allows Object Injection.This issue affects TotalContest Lite: from n/a through <= 2.9.1.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A flaw in TotalContest Lite for WordPress could let a low-privileged attacker abuse unsafe data deserialization. The published scoring indicates limited confidentiality, integrity, and availability impact. Business risk is concentrated on WordPress sites running TotalContest Lite through version 2.9.1.

Executive priority

Handle in the normal vulnerability remediation cycle, with higher priority for public WordPress sites, sites with many user accounts, or sites where contests collect sensitive data.

Technical view

CVE-2026-0677 is CWE-502 deserialization of untrusted data in TotalSuite TotalContest Lite. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, scoring 6.3. Sources identify affected versions as TotalContest Lite through 2.9.1.

Likely exposure

Exposure is likely limited to WordPress installations with the TotalContest Lite plugin installed and at or below version 2.9.1. The CVSS vector requires low privileges, so unauthenticated exposure is not supported by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. It also does not provide exploit details, a gadget chain, or confirmed real-world abuse. Treat exploitation status as unconfirmed.

Researcher notes

Impact depends on reachable deserialization and available PHP object gadget paths, which are not documented in the provided sources. The affected-version metadata is partly sparse, so validate against the plugin package name and installed version rather than CPE matching.

Mitigation direction

  • Inventory WordPress sites for TotalContest Lite installations.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed version.
  • Update if an official patched release is available.
  • Disable or remove the plugin where it is not business-critical.
  • Limit low-privileged WordPress accounts to necessary users only.

Validation and detection

  • Confirm whether TotalContest Lite is installed on each WordPress site.
  • Record the installed plugin version and compare it with 2.9.1.
  • Review vendor or Patchstack advisories for current remediation status.
  • Check WordPress user roles for unnecessary low-privileged accounts.
  • Monitor plugin-related logs for unusual authenticated activity.
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-0677 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
Medium
CVSS
6.3 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

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
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.83.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2026-0677Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TotalSuiteTotalContest Litetotalcontest-lite, 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.