dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-32210

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
Missing Authorization vulnerability in CreativeMindsSolutions CM Registration and Invitation Codes cm-invitation-codes allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CM Registration and Invitation Codes: from n/a through <= 2.5.6.

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

Missing authorization vulnerability in the CM Registration and Invitation Codes WordPress plugin allows unauthenticated or improperly authorized users to access registration and invitation code functionality that should be restricted, due to incorrectly configured access control security levels.

MitigationApply vendor patch (version 2.5.7 or later) which adds proper authorization checks to registration and invitation code endpoints; until patched, restrict access to registration pages via server-level controls or disable public registration.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect wp-content/plugins/ directory for cm-registration-invitation-codes folder
    Affected if The CM Registration and Invitation Codes plugin is present on the WordPress site
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > click on the plugin to view version details, or read the main plugin PHP file header for 'Version:' value
    Affected if The installed version is earlier than 2.5.7 (vulnerable versions: < 2.5.7)
  3. Verify registration page is publicly accessible
    Visit the registration page URL (typically /register or /registration, check plugin settings for configured endpoint) while logged out
    Affected if Unauthenticated users can access the registration form without any redirect to login
  4. Test invitation code endpoint exposure
    Attempt to access the invitation code validation endpoint (commonly /?cm_ric_validate=1 or similar, check plugin admin for configured URL) without authentication
    Affected if The endpoint returns valid responses to unauthenticated requests rather than requiring authorization

A user is affected if the CM Registration and Invitation Codes plugin is installed with a version lower than 2.5.7 and the registration/invitation code functionality is accessible to unauthenticated visitors.

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

Apply vendor patch (version 2.5.7 or later) which adds proper authorization checks to registration and invitation code endpoints; until patched, restrict access to registration pages via server-level controls or disable public registration.

Recommended fix Moderate confidence

Latest available version on WordPress.org (check for version > 2.5.6)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'CM Registration and Invitation Codes' (cm-invitation-codes)
  4. Check the plugin version currently installed
  5. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/cm-invitation-codes/ and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the new version number in the plugins list
  7. Test registration and invitation code functionality to ensure the plugin still works correctly
Caveat Review plugin changelog for any configuration changes or deprecated features before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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