dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13312

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-05
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
The CRM Memberships plugin for WordPress is vulnerable to unauthorized membership tag creation due to a missing capability check on the 'ntzcrm_add_new_tag' function in all versions up to, and including, 2.5. This makes it possible for unauthenticated attackers to create arbitrary membership tags and modify CRM configuration that should be restricted to administrators.

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 CRM Memberships WordPress plugin has a missing capability check on the 'ntzcrm_add_new_tag' function, allowing unauthenticated attackers to create arbitrary membership tags. This is a privilege escalation vulnerability where an action restricted to administrators can be executed by any visitor to the site.

MitigationUpdate the CRM Memberships plugin to version 2.6 or later. If no patch is available, consider disabling the plugin or blocking the vulnerable endpoint at the server level while a fix is developed.

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. Verify CRM Memberships plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins. Look for 'CRM Memberships' or 'CRM Memberships by [developer]' in the plugin list.
    Affected if The CRM Memberships plugin appears in the installed plugins list.
  2. Identify the installed plugin version
    In the Plugins page, click on the plugin name or 'View details' link for CRM Memberships. Note the version number displayed.
    Affected if The installed version is lower than 2.6 (e.g., 2.5.x, 2.4.x, or any version below 2.6).
  3. Check for the vulnerable AJAX endpoint
    Inspect the plugin files (typically in wp-content/plugins/ directory) for the function 'ntzcrm_add_new_tag'. Look in the main plugin PHP file or any AJAX handler files for how this function is hooked (e.g., add_action('wp_ajax_ntzcrm_add_new_tag', ...) or similar).
    Affected if The function 'ntzcrm_add_new_tag' exists and is hooked to an AJAX action without a capability check (e.g., no current_user_can() verification).
  4. Test unauthenticated access to the endpoint
    Send a POST request to your site's wp-admin/admin-ajax.php with action=ntzcrm_add_new_tag and a sample tag name parameter (e.g., tag_name=TestTag). Check if the response indicates success without requiring authentication.
    Affected if The request succeeds and returns a successful response (e.g., success: true) without being logged in or without proper capability verification.
  5. Review existing membership tags for unauthorized changes
    In WordPress admin, navigate to the CRM Memberships settings or tag management area. List all membership tags and look for any tags that were not created by an administrator you recognize.
    Affected if There are membership tags present that were created unexpectedly or by unknown users.

If the CRM Memberships plugin is installed at a version below 2.6 and the ntzcrm_add_new_tag function is accessible without authentication, the environment is affected by this vulnerability.

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 CRM Memberships plugin to version 2.6 or later. If no patch is available, consider disabling the plugin or blocking the vulnerable endpoint at the server level while a fix is developed.

Recommended fix Moderate confidence

Update to the latest version of CRM Memberships plugin (version higher than 2.5) from the WordPress plugin repository

  1. Check the current version of the CRM Memberships plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the CRM Memberships plugin and verify the current version number
  4. If the installed version is 2.5 or lower, update to the latest available version from the WordPress plugin repository
  5. Go to Plugins > Add New > Upload Plugin (or use WordPress automatic updates if enabled)
  6. Update to the latest version that includes the security fix for the missing capability check
  7. After updating, verify that only administrators can access the membership tag creation functionality
Caveat Review plugin settings after upgrade as any configuration changes may need reapplication

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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