CVE-2025-14854
Unauthorized Access in WP-CRM Plugin Exposes Emails, Modifies Tasks
Publication date: 2026-01-14
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | wp_crm_system | to 3.4.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-14854 is a vulnerability in the WP-CRM System WordPress plugin (up to version 3.4.5) where two AJAX functions, wpcrm_get_email_recipients and wpcrm_system_ajax_task_change_status, lack proper capability checks. This means that authenticated users with subscriber-level access or higher can exploit these AJAX endpoints to enumerate CRM contact email addresses (disclosing personally identifiable information) and modify CRM task statuses without proper authorization. The plugin relies only on nonce verification for security but does not verify user permissions, leading to unauthorized access and modification of CRM data. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing authenticated users with minimal privileges (subscriber level and above) to access sensitive CRM contact email addresses, leading to disclosure of personally identifiable information (PII). Additionally, these users can modify CRM task statuses, potentially disrupting task management and workflow integrity. This unauthorized access and modification can compromise data confidentiality and integrity within your CRM system. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively affect compliance with standards and regulations such as GDPR and HIPAA because it allows unauthorized disclosure of personally identifiable information (PII) through enumeration of CRM contact email addresses. Unauthorized access and modification of sensitive data violate data protection principles required by these regulations, potentially leading to legal and regulatory consequences. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring AJAX requests to the WP-CRM System plugin's endpoints, specifically the AJAX actions 'wp_ajax_task_list_response' and 'wp_ajax_task_change_status'. You can look for unauthorized or suspicious AJAX POST requests targeting these actions. Since the vulnerability involves missing capability checks, any authenticated user with subscriber-level access making these AJAX calls could indicate exploitation attempts. Commands to detect such activity could include inspecting web server logs or using tools like curl to test the endpoints. For example, you can use curl to simulate an AJAX request to the task status change endpoint: curl -X POST -d 'action=task_change_status&post_id=123&task_status=completed&nonce=VALID_NONCE' https://yourwordpresssite.com/wp-admin/admin-ajax.php. Additionally, monitoring for unusual changes in CRM task statuses or unexpected enumeration of email addresses in logs may help detect exploitation. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the WP-CRM System plugin to a version later than 3.4.5 where the vulnerability is fixed. If an update is not immediately available, restrict access to the AJAX endpoints by implementing additional capability checks or access controls to ensure only authorized users can invoke the affected AJAX functions. You can also disable or restrict subscriber-level users from accessing the plugin's AJAX actions. Monitoring and auditing user activity related to CRM tasks and email recipient enumeration is recommended. Applying web application firewall (WAF) rules to block suspicious AJAX requests targeting these endpoints can also help mitigate exploitation. [1]