dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14854

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
The WP-CRM System plugin for WordPress is vulnerable to unauthorized access due to missing capability checks on the wpcrm_get_email_recipients and wpcrm_system_ajax_task_change_status AJAX functions in all versions up to, and including, 3.4.5. This makes it possible for authenticated attackers, with subscriber level access and above, to enumerate CRM contact email addresses (PII disclosure) and modify CRM task statuses. CVE-2025-62106 is likely a duplicate of this issue.

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

The WP-CRM System WordPress plugin lacks capability checks on two AJAX endpoints (wpcrm_get_email_recipients and wpcrm_system_ajax_task_change_status), allowing any authenticated user with subscriber-level privileges to access sensitive CRM contact email addresses and modify task statuses. This is a classic Insecure Direct Object Reference (IDOR) combined with missing authorization vulnerability.

MitigationAdd proper capability checks (e.g., current_user_can()) to both AJAX functions to verify the user has appropriate CRM permissions before returning contact data or allowing task status changes. Update to the latest plugin 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Verify WP-CRM System plugin is installed
    Check the WordPress plugins directory or access wp-admin > Plugins to confirm WP-CRM System is active. Note the installed version number.
    Affected if WP-CRM System plugin is installed and active
  2. Identify the installed plugin version
    In wp-admin > Plugins, find WP-CRM System and record the version number displayed. Compare this to the latest version on the WordPress plugin repository.
    Affected if Installed version lacks the capability check fixes for the two AJAX endpoints
  3. Test AJAX endpoint accessibility for email recipients
    Send a GET or POST request to wp-admin/admin-ajax.php with action=wpcrm_get_email_recipients while logged in as a low-privilege user (subscriber role). Observe if the response contains CRM contact email addresses without a capability error.
    Affected if The endpoint returns contact email data without requiring elevated permissions
  4. Test AJAX endpoint accessibility for task status changes
    Send a POST request to wp-admin/admin-ajax.php with action=wpcrm_system_ajax_task_change_status and a task ID/status parameter while logged in as a subscriber-level user. Observe if the task status is modified without a capability error.
    Affected if The endpoint allows status changes without verifying user permissions
  5. Check for subscriber-level user accounts
    In wp-admin > Users, review the list of users and identify any accounts assigned the Subscriber role. These users would be able to exploit the vulnerability if the endpoints lack capability checks.
    Affected if Subscriber-role users exist and can authenticate to the site

A user is affected if the WP-CRM System plugin is installed and its version does not include proper capability checks on the wpcrm_get_email_recipients and wpcrm_system_ajax_task_change_status AJAX endpoints, allowing subscriber-level users to access contact emails or modify task statuses.

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

Add proper capability checks (e.g., current_user_can()) to both AJAX functions to verify the user has appropriate CRM permissions before returning contact data or allowing task status changes. Update to the latest plugin version once available.

Recommended fix Moderate confidence

WP-CRM System version 3.4.6 or newer

  1. Update the WP-CRM System plugin to version 3.4.6 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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