dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-27301

HIGH · 7.2 CVSS v3.1 Published 2025-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 Nazmul Hasan Robin NHR Options Table Manager nhrrob-options-table-manager allows Object Injection.This issue affects NHR Options Table Manager: from n/a through <= 1.1.2.

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 a PHP Object Injection vulnerability in the NHR Options Table Manager WordPress plugin. The plugin deserializes untrusted data (likely via PHP's unsafe unserialize() function), allowing attackers to inject malicious PHP objects. This can lead to code execution, file deletion, or other attacks depending on available gadget chains in the plugin and WordPress environment.

MitigationReplace unsafe unserialize() calls with json_decode() or implement proper input validation/sanitization. Ensure no user-controlled data reaches deserialization functions. Update the plugin to the latest version once 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
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 NHR Options Table Manager plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'nhr-options-table-manager' or similar. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to confirm the plugin is listed.
    Affected if The plugin appears in the list of installed WordPress plugins.
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually in wp-content/plugins/nhr-options-table-manager/ or similar folder name) and look for the plugin header comment containing 'Version: x.x.x'. Alternatively, check the readme.txt file in the plugin directory for the version number.
    Affected if The plugin version is present and can be compared against any fixed version once released.
  3. Locate unsafe deserialization calls in plugin code
    Search the plugin directory for PHP files containing 'unserialize(' function calls. Use grep or similar: grep -r "unserialize" wp-content/plugins/nhr-options-table-manager/
    Affected if The plugin code contains unserialize() calls that process data without prior sanitization.
  4. Determine if user input reaches the deserialization sink
    Review the code paths leading to the unserialize() calls identified in step 3. Trace back to determine if $_GET, $_POST, $_COOKIE, or database values are passed to unserialize() without validation.
    Affected if User-controlled data (from request parameters, stored options, or external sources) flows into the unserialize() function.
  5. Check plugin accessibility
    Verify whether the vulnerable code is accessible to unauthenticated users, authenticated users, or only administrators by reviewing the code for capability checks or nonce verification around the deserialization endpoint.
    Affected if The vulnerable deserialization function can be triggered by users with limited or no privileges.

If the NHR Options Table Manager plugin is installed, contains unserialize() calls processing user input, and those calls are accessible to attackers, the environment is vulnerable to CVE-2025-27301.

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 unserialize() calls with json_decode() or implement proper input validation/sanitization. Ensure no user-controlled data reaches deserialization functions. Update the plugin to the latest version once available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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