LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25031: WordPress Tasty Daily theme < 1.27 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in park_of_ideas Tasty Daily tastydaily allows Object Injection.This issue affects Tasty Daily: from n/a through < 1.27.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-25031 affects the WordPress Tasty Daily theme before version 1.27. It is rated critical because a remote, unauthenticated attacker may trigger unsafe PHP deserialization, potentially compromising the site’s confidentiality, integrity, and availability. No provided source confirms active exploitation.

Executive priority

Treat as urgent for any public WordPress site using Tasty Daily. The severity is critical and the attack requires no login or user action per CVSS. Patch or remove affected deployments quickly, while noting that active exploitation is not confirmed by the provided sources.

Technical view

The issue is CWE-502 deserialization of untrusted data in park_of_ideas Tasty Daily (tastydaily), affecting versions through <1.27. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, score 9.8. Public detail is limited to the CVE record and Patchstack entry.

Likely exposure

Exposure is likely limited to WordPress sites using the Tasty Daily theme below version 1.27. Internet-facing WordPress sites are the primary concern. The provided data does not identify affected managed hosting platforms, plugins, or non-WordPress products.

Exploitation context

The CVSS vector indicates network reachability, low attack complexity, no privileges, and no user interaction. The source bundle does not include exploit code, proof-of-concept details, or confirmation of exploitation in the wild. It is not listed as KEV in the provided data.

Researcher notes

Evidence is sparse. The CVE entry identifies unsafe deserialization and Patchstack is the only vulnerability database reference in the bundle. No vulnerable parameter, exploit chain, or gadget requirements are provided. Validate exposure through asset inventory rather than assumptions.

Mitigation direction

  • Inventory WordPress sites for the Tasty Daily theme.
  • Update Tasty Daily to version 1.27 or later if available.
  • If unable to update, disable or replace the theme.
  • Review Patchstack and vendor guidance for any additional remediation.
  • Prioritize internet-facing and business-critical WordPress sites first.

Validation and detection

  • Confirm whether Tasty Daily is installed on each WordPress site.
  • Record the installed theme version and compare it to 1.27.
  • Verify the site is no longer running an affected version.
  • Check security monitoring for suspicious WordPress activity.
  • Document exceptions where updates or replacement are delayed.
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-25031 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-25031Attack 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
park_of_ideasTasty Dailytastydaily, 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.