dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-31810

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in PickPlugins Question Answer question-answer allows Accessing Functionality Not Properly Constrained by ACLs.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 Missing Authorization vulnerability in the PickPlugins Question Answer WordPress plugin allows users to access functionality that should be restricted by Access Control Lists (ACLs). The plugin fails to properly enforce authorization checks on certain functions, potentially allowing unauthenticated or lower-privileged users to perform actions reserved for higher-privileged users.

MitigationUpdate to a patched version of the plugin once released. Until then, implement role-based access control checks and capability verification on all sensitive plugin functions, and consider deploying a WAF rule to restrict access to plugin endpoints.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 installation and version
    Navigate to WordPress Admin > Plugins and locate 'PickPlugins Question Answer' in the installed plugins list. Note the installed version from the plugin version column, or inspect the plugin's main PHP file (usually in wp-content/plugins/question-answer/) and read the Version header in the plugin comment block.
    Affected if The plugin is installed and the installed version is lower than the patched version released after CVE-2025-31810.
  2. Identify sensitive plugin functions lacking authorization
    Inspect the plugin's PHP files in wp-content/plugins/question-answer/ for functions that perform privileged actions (such as creating/editing questions, managing answers, changing user settings, or accessing admin functions). Look for function calls that execute database operations or modify content without current_user_can() or capability checks.
    Affected if Sensitive functions exist that do not perform capability checks before executing privileged operations.
  3. Test plugin endpoints for unauthorized access
    Using a low-privilege user account (subscriber or no role) or unauthenticated state, attempt to access plugin AJAX actions or direct function calls by inspecting the plugin's JavaScript files or form submissions. Look for wp_ajax_ or wp_ajax_nopriv_ hooks that handle sensitive operations.
    Affected if Plugin endpoints respond successfully to requests from unauthenticated or low-privilege users when they should return a permission error.
  4. Review user role and capability enforcement
    Check the plugin's role handling code (typically in includes files) to see if it properly validates user capabilities using functions like current_user_can(), check_admin_referer(), or nonce verification before allowing access to restricted features.
    Affected if The plugin grants access to administrative or privileged functions without verifying the current user's role or capability.

You are affected if the PickPlugins Question Answer plugin is installed and its code contains functions or endpoints that handle sensitive operations without proper authorization checks, allowing lower-privileged or unauthenticated users to access restricted functionality.

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 to a patched version of the plugin once released. Until then, implement role-based access control checks and capability verification on all sensitive plugin functions, and consider deploying a WAF rule to restrict access to plugin endpoints.

Recommended fix Moderate confidence

Upgrade to the latest version of the Question Answer plugin (version > 1.2.73) from the WordPress plugin repository

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Question Answer' (or 'PickPlugins Question Answer') plugin
  4. Check the current installed version to confirm it is <= 1.2.73
  5. Navigate to Plugins > Add New
  6. Search for 'Question Answer' or 'PickPlugins Question Answer'
  7. If an update is available, click 'Update Now' to install the latest version
  8. Alternatively, download the latest version from the official WordPress plugin repository and upload it manually

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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