CVE-2025-13313 CRITICAL

CVE-2025-13313: CRM Memberships <= 2.6 - Missing Authorization to Privilege Escalation via Unauthenticated Password Reset in 'ntzcrm_changepassword' AJAX Endpoint

Vendor Dripadmin
Product CRM Memberships
Weakness CWE-862 · Missing authorization
Published December 5, 2025
Last update April 8, 2026

CVSS base score

9.8/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity High

CVSS vector

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

What the vulnerability does

01Description

The CRM Memberships plugin for WordPress is vulnerable to privilege escalation via password reset in all versions up to, and including, 2.6. This is due to missing authorization and authentication checks on the `ntzcrm_changepassword` AJAX action. This makes it possible for unauthenticated attackers to reset arbitrary user passwords and gain unauthorized access to user accounts via the `ntzcrm_changepassword` endpoint, granted they can obtain or enumerate a target user's email address. The plugin also exposes the `ntzcrm_get_users` endpoint without authentication, allowing attackers to enumerate subscriber email addresses, facilitating the exploitation of the password reset vulnerability.

Explanation of Vulnerability in Simple Terms

02Summary

CRM Memberships versions 2.6 and earlier lack proper authorization checks, allowing unauthenticated attackers to read, modify, or delete data without logging in. The vulnerability affects all core functions of the application. Site administrators should update immediately to a version newer than 2.6.

What an attacker can do

03Attacker Capabilities

Read, modify, or delete any data in the CRM without authentication.

Potential impact on your site

04Site Impact

Complete compromise of CRM data: customer records, memberships, and transactions can be accessed or destroyed by anyone.

Conditions required to exploit

05Prerequisites

Network access only; no login or user interaction required.

Key dates

06Disclosure timeline

December 5, 2025 CVE published
April 8, 2026 Record updated