CVE-2025-60245
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 · uneditedDeserialization of Untrusted Data vulnerability in WP User Manager WP User Manager wp-user-manager allows Object Injection.This issue affects WP User Manager: from n/a through <= 2.9.12.
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 confidenceThe WP User Manager WordPress plugin <= 2.9.12 is vulnerable to PHP Object Injection via unsafe deserialization of untrusted data. Attackers can potentially exploit magic methods (__wakeup, __destruct, etc.) to achieve remote code execution, file operations, or SQL injection depending on available gadget chains in the application 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP User Manager plugin is installedIn WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'WP User Manager' in the list. Alternatively, check the /wp-content/plugins/wp-user-manager/ directory exists on the server.Affected if The plugin is installed and present in the WordPress environment
-
Check plugin activation statusIn WordPress admin > Plugins, verify whether WP User Manager is activated. Also check site for frontend widgets, shortcodes, or blocks that may be rendering WP User Manager functionality.Affected if The plugin is activated and in use on the site
-
Identify installed version numberIn WordPress admin > Plugins, click 'View Details' on WP User Manager to display the version number. Alternatively, open /wp-content/plugins/wp-user-manager/readme.txt and look for the 'Stable tag' or version header in the main plugin PHP file.Affected if The version is 2.9.12 or lower (any version <= 2.9.12 is affected)
-
Determine if plugin handles serialized dataSearch plugin files for unserialize() function calls that process user-supplied input: grep -r 'unserialize' /wp-content/plugins/wp-user-manager/ and examine if any unserialize() calls accept data from request parameters, user meta, or database fields without validation.Affected if The plugin contains unserialize() calls processing untrusted input - this is the vulnerable condition that enables the object injection
If WP User Manager is installed at version 2.9.12 or lower and contains unserialize() calls handling external input, the environment is affected by this PHP Object Injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataImmediately update WP User Manager to the latest patched version. Conduct a security audit of the WordPress installation for signs of compromise, as object injection vulnerabilities can be leveraged for remote code execution.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60245 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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