dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-49438

HIGH · 8.1 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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 Max Chirkov Simple Login Log allows Object Injection. This issue affects Simple Login Log: from n/a through 1.1.3.

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

The Simple Login Log WordPress plugin has a PHP Object Injection vulnerability due to unsafe deserialization (likely use of unserialize() on untrusted data). An attacker can craft malicious serialized PHP objects that, when deserialized, can trigger magic methods to achieve code execution, read files, or perform other attacks depending on available gadget chains in the WordPress environment.

MitigationUpdate to the latest version of Simple Login Log which should replace unsafe deserialization with json_encode/json_decode or implement proper input validation. If no update exists, disable the plugin until a fix is available.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 Simple Login Log plugin files
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'simple-login-log' or similar variant. List all plugin directories to confirm presence.
    Affected if The plugin directory exists in wp-content/plugins/ and contains PHP files belonging to Simple Login Log.
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually simple-login-log.php or similar) and look for the plugin header comment which typically contains 'Version: x.x.x'. Alternatively, check the readme.txt file in the plugin directory for the version field.
    Affected if The plugin is installed and you can determine its version number from the plugin header or readme.txt.
  3. Search for unsafe deserialization in plugin code
    Within the plugin directory, search all PHP files for the string 'unserialize(' using grep, a file search tool, or manually opening and searching each PHP file.
    Affected if Any PHP file in the plugin contains 'unserialize(' which is called on data that could be influenced by user input (such as $_POST, $_GET, $_COOKIE, or data stored in the database from login attempts).
  4. Verify if login data is stored and could be deserialized
    Examine the plugin's login handling functions to determine if user-supplied input (such as username, IP address, or user agent) is saved to the WordPress database and later retrieved for deserialization.
    Affected if The plugin stores login attempt data in the WordPress database and later retrieves and deserializes this data without proper validation.
  5. Check plugin activity status
    In the WordPress admin dashboard under Plugins > Installed Plugins, verify if Simple Login Log is activated. Alternatively, query the wp_options table for the plugin's active status.
    Affected if The plugin is activated and running on the WordPress site, making the vulnerable code path executable.

You are affected if the Simple Login Log plugin is installed and active, contains code using unserialize() on user-influenced data, and your WordPress environment has gadget chains available for PHP Object Injection exploitation.

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

Update to the latest version of Simple Login Log which should replace unsafe deserialization with json_encode/json_decode or implement proper input validation. If no update exists, disable the plugin until a fix is available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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