dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67956

HIGH · 8.2 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in wpeverest User Registration user-registration allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects User Registration: from n/a through <= 4.4.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

A missing authorization vulnerability in the User Registration WordPress plugin by wpeverest allows attackers to exploit incorrectly configured access control security levels. This could enable unauthorized access to registration-related functionality or data that should be restricted based on user roles or permissions.

MitigationUpdate to the latest version of the User Registration plugin when available, or implement additional access control measures at the application or server level to enforce proper authorization checks.

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
High
Availability
Low

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

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 User Registration plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'User Registration' by wpeverest. Note whether it is active or inactive.
    Affected if The plugin is installed and active, exposing the affected functionality.
  2. Determine installed plugin version
    Click 'View details' on the User Registration plugin in the Plugins list, or check the plugin files in wp-content/plugins/user-registration/ for a version.php or readme.txt file containing the version number.
    Affected if The installed version is any version prior to the patched release containing the authorization fix.
  3. Review plugin access control settings
    Navigate to User Registration > Settings in the WordPress admin. Check all tabs (especially General, Security, and Roles) for any misconfigured options related to who can access registration features, create users, or view registration data.
    Affected if Access control is incorrectly configured allowing lower-privileged users or unauthenticated users to access restricted registration functionality.
  4. Inspect user role and capability assignments
    Go to Users > Roles or User Registration > User Roles. Examine whether any custom roles have been granted capabilities (such as 'create_users', 'manage_options', or 'user_registration_access') that they should not possess based on their intended permission level.
    Affected if Roles have been assigned elevated capabilities that bypass proper authorization checks.
  5. Test registration endpoint access controls
    Using a browser or HTTP tool, attempt to access registration-related pages or AJAX endpoints (such as /wp-admin/admin-ajax.php?action=user_registration_*) while logged out or as a low-privilege user. Observe whether unauthorized actions are permitted.
    Affected if Unauthenticated or low-privilege users can access or execute registration-related functionality they should not be able to reach.

You are affected if the User Registration plugin by wpeverest is active in your WordPress installation and access control settings or role configurations allow unauthorized access to registration functionality.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the User Registration plugin when available, or implement additional access control measures at the application or server level to enforce proper authorization checks.

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-67956 — 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-67956 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