dbcve.org
Sunshine Photo CartWordPress extension · Sunshinephotocart

CVE-2025-31084

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 3.4.11 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 sunshinephotocart Sunshine Photo Cart sunshine-photo-cart allows Object Injection.This issue affects Sunshine Photo Cart: from n/a through <= 3.4.10.

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 Sunshine Photo Cart WordPress plugin. The plugin deserializes untrusted data (likely via PHP's unsafe unserialize() function), allowing attackers to inject crafted PHP objects. With available POP chains, this can lead to remote code execution. The critical 9.8 CVSS indicates unauthenticated, network-exploitable code execution.

MitigationUpdate to a patched version of Sunshine Photo Cart. If no patched version exists, disable the plugin until remediation is available. The fix typically involves replacing unsafe unserialize() calls with safe alternatives like json_decode().

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
Sunshine Photo CartWordPress extension
Affected:< 3.4.11

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. Verify Sunshine Photo Cart plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Sunshine Photo Cart' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'sunshinephotocart'.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, click on the Sunshine Photo Cart plugin to view details and read the version number. Alternatively, open /wp-content/plugins/sunshinephotocart/readme.txt and check the version in the header section.
    Affected if Version is less than 3.4.11 (e.g., 3.4.10, 3.4.9, etc.)
  3. Locate unsafe unserialize() calls in plugin source
    Search the plugin directory for PHP files containing 'unserialize(' - run: grep -r "unserialize(" /wp-content/plugins/sunshinephotocart/ or use a file search in your IDE/code editor.
    Affected if Files contain unserialize() calls that process untrusted input (e.g., from $_POST, $_GET, or database fields without validation)
  4. Check if deserialized data comes from user input
    Examine identified unserialize() calls in context - determine if the data being deserialized originates from any user-controllable source (request parameters, logged data, database content that could be manipulated).
    Affected if Unserialize is called on data from $_REQUEST, $_POST, $_GET, or other external sources without prior sanitization

You are affected if Sunshine Photo Cart plugin version is below 3.4.11 AND the plugin contains unserialize() calls that process user-supplied data.

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 3.4.11 or later
Fixed in 3.4.11
Interim mitigation

Update to a patched version of Sunshine Photo Cart. If no patched version exists, disable the plugin until remediation is available. The fix typically involves replacing unsafe unserialize() calls with safe alternatives like json_decode().

Recommended fix High confidence

3.4.11

  1. Upgrade Sunshine Photo Cart to version 3.4.11 or later

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

Fix this in Sunshine Photo Cart Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,870
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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