dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-32647

HIGH · 8.8 CVSS v3.1 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 PickPlugins Question Answer question-answer allows Object Injection.This issue affects Question Answer: from n/a through <= 1.2.73.

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 deserialization of untrusted data vulnerability in the PickPlugins Question Answer WordPress plugin allows unauthenticated attackers to inject PHP objects (Object Injection), potentially leading to remote code execution. This is a critical insecure deserialization issue common in PHP applications using unserialize() with user-controlled input.

MitigationUpdate the PickPlugins Question Answer plugin to version 1.2.74 or later once available, or remove the plugin if no patch is released. Consider implementing input validation and restricting unserialize() usage as an immediate workaround.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm plugin is installed
    Check if the PickPlugins Question Answer plugin directory exists at wp-content/plugins/question-answer/ in the WordPress filesystem
    Affected if The plugin directory exists on the server
  2. Identify installed plugin version
    Open the main plugin file (typically question-answer.php) in wp-content/plugins/question-answer/ and locate the Version header comment or $version variable
    Affected if The reported version is below 1.2.74 or the version cannot be determined
  3. Verify plugin is active
    Check WordPress admin under Plugins > Installed Plugins, or query the wp_options table for the active_plugins option to confirm the plugin is enabled
    Affected if The plugin appears in the list of active plugins
  4. Locate vulnerable deserialization code
    Search plugin PHP files for the pattern unserialize() using grep or a file search: grep -r 'unserialize' wp-content/plugins/question-answer/
    Affected if Files containing unserialize() are found and the input source is user-controlled (request parameters, POST/GET data)
  5. Identify attack surface endpoints
    Review plugin AJAX handlers and form processing files for any $_GET, $_POST, or $_REQUEST usage feeding into unserialize() calls
    Affected if User-supplied input from request parameters is passed directly to unserialize()

A user is affected if the PickPlugins Question Answer plugin is installed, active, and running a version prior to 1.2.74 with unserialize() handling user-controlled input.

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 the PickPlugins Question Answer plugin to version 1.2.74 or later once available, or remove the plugin if no patch is released. Consider implementing input validation and restricting unserialize() usage as an immediate workaround.

Recommended fix Moderate confidence

Latest available version from wordpress.org repository (version higher than 1.2.73)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'PickPlugins Question Answer' plugin
  4. 4. Check the current installed version (should be <= 1.2.73)
  5. 5. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org
  6. 6. Verify the updated version is installed (should be higher than 1.2.73)

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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 locally
dbcve dependency scanner

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