dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-27417

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A PHP Object Injection vulnerability exists in the Sweet Date WordPress plugin due to unsafe deserialization of untrusted data. Attackers can potentially craft malicious serialized PHP objects to achieve remote code execution by leveraging available POP (Property Oriented Programming) gadgets in the application or bundled libraries.

MitigationUpdate Sweet Date plugin to version 4.0.1 or later immediately. If immediate update is not possible, disable the plugin to prevent exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Sweet Date plugin installation
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named sweet-date or similar, or access Plugins > Installed Plugins in WordPress admin panel
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    Open the main plugin file (usually sweet-date.php or index.php inside the plugin folder) and locate the 'Version' header comment in the plugin file metadata
    Affected if Version number cannot be determined or is below 4.0.1
  3. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm Sweet Date status shows as 'Active'
    Affected if Plugin is currently active and version is below 4.0.1
  4. Compare version against affected range
    Compare the identified version number to the fixed version 4.0.1. Any version lower than 4.0.1 falls within the vulnerable range
    Affected if Installed version is lower than 4.0.1

If the Sweet Date WordPress plugin is installed, active, and running a version lower than 4.0.1, the environment is affected by this PHP Object Injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Sweet Date plugin to version 4.0.1 or later immediately. If immediate update is not possible, disable the plugin to prevent exploitation.

Recommended fix High confidence

4.0.1

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Sweet Date' by SeventhQueen
  4. If the plugin shows version lower than 4.0.1, click 'Update Now' to upgrade to version 4.0.1 or latest available version
  5. After update, verify the running version is 4.0.1 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27417 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27417 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data