dbcve.org
Sweet DessertWordPress extension · Axiomthemes

CVE-2025-49073

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-06
Fix available
A fix is available. Upgrade to 1.1.13 or later.
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 axiomthemes Sweet Dessert sweet-dessert allows Object Injection.This issue affects Sweet Dessert: from n/a through < 1.1.13.

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 · moderate confidence

This is a PHP Object Injection vulnerability in the Sweet Dessert WordPress theme. The theme deserializes untrusted data without proper validation, allowing an unauthenticated attacker to inject malicious PHP objects and potentially achieve remote code execution.

MitigationUpdate the Sweet Dessert theme to version 1.1.13 or later. If immediate updating is not possible, disable the theme and implement web application firewall rules to detect deserialization payloads.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sweet DessertWordPress extension
Affected:< 1.1.13

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 the Sweet Dessert theme version
    Navigate to wp-content/themes/sweet-dessert/style.css and look for the 'Version:' declaration in the file header, or check the theme's functions.php for the version define.
    Affected if The version listed is lower than 1.1.13 (e.g., 1.1.12, 1.1.0, etc.) or no version is displayed in the header.
  2. Verify the theme is active
    In the WordPress admin dashboard, go to Appearance > Themes and confirm Sweet Dessert is the active theme.
    Affected if The Sweet Dessert theme is currently activated on the WordPress site.
  3. Search for insecure deserialization patterns
    In the theme directory (wp-content/themes/sweet-dessert/), search for the PHP function 'unserialize(' using grep, grep -r "unserialize(" . in the theme folder, or a file search in a code editor.
    Affected if Any file in the theme contains a call to unserialize() that processes data from user input ($_GET, $_POST, $_REQUEST, or cookies) without prior sanitization.
  4. Identify input entry points reaching deserialization
    Examine files containing unserialize() calls. Trace whether $_GET, $_POST, $_REQUEST, or $_COOKIE variables are passed directly to the unserialize() function.
    Affected if User-controlled data (from GET/POST parameters or cookies) flows directly into an unserialize() call without validation.
  5. Check for known vulnerable files
    Examine common AJAX handlers or callback files in the theme, such as functions.php, includes files in the theme folder, or any file handling AJAX actions.
    Affected if The theme contains AJAX handlers or callback functions that accept and unserialize data from external sources.

You are affected if the Sweet Dessert theme version is below 1.1.13 AND the theme contains insecure unserialize() calls that process untrusted user input.

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
Upgrade available Upgrade to 1.1.13 or later
Fixed in 1.1.13
Interim mitigation

Update the Sweet Dessert theme to version 1.1.13 or later. If immediate updating is not possible, disable the theme and implement web application firewall rules to detect deserialization payloads.

Recommended fix High confidence

1.1.13 or later

  1. Update the Sweet Dessert theme to version 1.1.13 or later through your WordPress dashboard (Appearance > Themes) or contact your theme provider for the latest version

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

Fix this in Sweet Dessert Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49073 — 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-2025-49073 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