dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-22526

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-28
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 mywebtonet PHP/MySQL CPU performance statistics mywebtonet-performancestats allows Object Injection.This issue affects PHP/MySQL CPU performance statistics: from n/a through <= 1.2.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 · moderate confidence

A PHP Object Injection vulnerability exists in mywebtonet-performancestats through version 1.2.1, where untrusted data is deserialized without proper validation. This can allow attackers to inject malicious PHP objects into the application context, potentially leading to remote code execution depending on available magic methods in the application or loaded libraries.

MitigationReplace unsafe PHP deserialization (unserialize()) with safer alternatives such as JSON encoding/decoding, or implement strict allowlist validation if deserialization is absolutely required. Also ensure all available library components are updated to mitigate gadget chain 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 the mywebtonet-performancestats component
    Search your codebase, plugins directory, or installed packages for files or directories containing 'mywebtonet-performancestats' or 'performancestats'. Check your composer.json, plugin manifests, or application includes.
    Affected if The component is found in your environment and has not been removed or replaced.
  2. Determine the installed version
    Open the main PHP file for this component (often named performancestats.php or similar) and look for a version constant, comment header, or check the package manifest/composer.json version field.
    Affected if The version is 1.2.1 or any earlier version within the 1.x line.
  3. Identify deserialization code paths
    Search the component source code for occurrences of 'unserialize(' function calls. Examine the data source being passed to unserialize() - look for input from $_GET, $_POST, $_REQUEST, cookies, or database fields.
    Affected if The component contains unserialize() calls that process data originating from user-supplied sources without prior validation.
  4. Verify no input sanitization before deserialization
    Examine the code around each unserialize() call. Check if there is any validation, sanitization, or allowlist filtering applied to the input before it reaches unserialize(). Look for filtering functions, type checks, or signature validation.
    Affected if Raw untrusted data flows directly to unserialize() without any validation layer.
  5. Check for magic methods that could be exploited
    Search the component and any included libraries for __wakeup, __destruct, __toString, __get, or __call magic method definitions. These can be chained with the object injection for RCE.
    Affected if Magic methods exist in the application or loaded libraries that could form a gadget chain with the injected objects.

You are affected if mywebtonet-performancestats version 1.2.1 or earlier is installed and your application deserializes untrusted data via unserialize() without validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace unsafe PHP deserialization (unserialize()) with safer alternatives such as JSON encoding/decoding, or implement strict allowlist validation if deserialization is absolutely required. Also ensure all available library components are updated to mitigate gadget chain exploitation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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