dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-27410

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Unauthenticated Deserialization of untrusted data in Slimstat Analytics < 5.4.0 versions.

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

This is an insecure deserialization vulnerability in the Slimstat Analytics WordPress plugin versions prior to 5.4.0. The plugin uses PHP's unserialize() function on untrusted data without proper validation, allowing unauthenticated attackers to craft malicious serialized PHP objects that could potentially achieve remote code execution through PHP object injection.

MitigationUpdate Slimstat Analytics to version 5.4.0 or later which contains the patch for this vulnerability. As this is a critical security update, apply it immediately after testing in a non-production environment.

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify installed Slimstat Analytics version
    In WordPress admin, go to Plugins > Installed Plugins > Slimstat Analytics and read the version number. Alternatively, check the main plugin file (e.g., slimstat.php) in wp-content/plugins/ for the 'Version' header.
    Affected if The version shown is lower than 5.4.0 (e.g., 5.3.x, 5.2.x, etc.)
  2. Confirm plugin is active
    Verify that Slimstat Analytics is enabled in your WordPress site via Plugins > Installed Plugins. The vulnerability only applies when the plugin is active.
    Affected if The plugin is activated and running on the site.
  3. Check for unserialize usage in plugin code
    Search plugin source files for calls to unserialize() function, particularly those processing $_GET, $_POST, $_REQUEST, or $_COOKIE superglobals without sanitization.
    Affected if The plugin code contains unserialize() calls handling untrusted input from HTTP requests.
  4. Inspect server access logs for exploitation attempts
    Review web server access logs (Apache/Nginx) for requests to paths containing 'slimstat' with suspicious serialized data patterns (e.g., O: followed by numbers, C: for custom, a: for arrays) in query parameters or request bodies.
    Affected if Log entries show unserialize-like payloads being sent to slimstat endpoints.

You are affected if Slimstat Analytics plugin version is below 5.4.0 and the plugin is currently active on your WordPress site.

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 Slimstat Analytics to version 5.4.0 or later which contains the patch for this vulnerability. As this is a critical security update, apply it immediately after testing in a non-production environment.

Recommended fix Moderate confidence

Slimstat Analytics version 5.4.0 or later

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Update Slimstat Analytics plugin to version 5.4.0 or later through the WordPress admin dashboard (Plugins > Add New > Upload or WordPress repository), or via FTP/sftp by replacing the plugin files.
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin.
  4. 4. Test that the Slimstat Analytics functionality works correctly after the update.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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