LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27417: WordPress Sweet Date theme < 4.0.1 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in SeventhQueen Sweet Date sweetdate allows Object Injection.This issue affects Sweet Date: from n/a through < 4.0.1.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-27417 is a critical vulnerability in the WordPress Sweet Date theme before 4.0.1. Public records describe unsafe deserialization that can allow PHP object injection. The CVSS score is 9.8, indicating potential full compromise impact. No provided source confirms active exploitation or CISA KEV listing.

Executive priority

Prioritize remediation within the normal critical-vulnerability SLA, especially for public WordPress sites. The business risk is potential site compromise, data exposure, or service disruption. There is no provided evidence of active exploitation, but the severity and remote attack profile justify rapid action.

Technical view

The issue is CWE-502, Deserialization of Untrusted Data, in SeventhQueen Sweet Date. The CVSS vector indicates network access, low complexity, no privileges, and no user interaction. Affected versions are reported as Sweet Date before 4.0.1. The public bundle does not provide vulnerable endpoint details, proof-of-concept behavior, or exploit prerequisites beyond CVSS metadata.

Likely exposure

Internet-facing WordPress sites using the Sweet Date theme below 4.0.1 are the primary exposure. Sites not using this theme are not indicated as affected. Exposure should be prioritized where the theme is active, publicly reachable, or present on high-value WordPress properties.

Exploitation context

The CVSS data suggests remote unauthenticated exploitation may be possible, but the provided sources do not confirm exploitation in the wild. The issue is not marked as KEV in the bundle. Treat as urgent due to critical severity and WordPress internet exposure, while avoiding assumptions about exploit availability.

Researcher notes

Public detail is limited to CVE metadata and Patchstack’s vulnerability entry. Do not assume gadget chains, endpoints, or exploit mechanics from the record alone. Validate affected deployments by theme version and monitor advisory updates for richer technical indicators or confirmed fixes.

Mitigation direction

  • Identify all WordPress sites using the Sweet Date theme.
  • Update Sweet Date to 4.0.1 or later if available.
  • If update is unavailable, follow SeventhQueen or Patchstack guidance.
  • Remove or disable unused Sweet Date installations.
  • Prioritize internet-facing and business-critical WordPress sites.

Validation and detection

  • Confirm whether Sweet Date is installed on each WordPress site.
  • Record the installed Sweet Date version.
  • Flag any version below 4.0.1 as affected.
  • Review vendor and Patchstack advisories for current remediation details.
  • Monitor WordPress and web logs for unusual 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-27417 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-27417Attack 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
SeventhQueenSweet Datesweetdate, 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.