dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-6215

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-23
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 Omnishop plugin for WordPress is vulnerable to Unauthenticated Registration Bypass in all versions up to, and including, 1.0.9. Its /users/register endpoint is exposed to the public (permission_callback always returns true) and invokes wp_create_user() unconditionally, ignoring the site’s users_can_register option and any nonce or CAPTCHA checks. This makes it possible for unauthenticated attackers to create arbitrary user accounts (customer) on sites where registrations should be closed.

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 Omnishop WordPress plugin has a registration bypass vulnerability in versions up to 1.0.9. The /users/register endpoint's permission_callback function unconditionally returns true, allowing any unauthenticated request to create user accounts via wp_create_user() without checking the site's users_can_register setting or validating nonces or CAPTCHAs.

MitigationRestrict the /users/register endpoint by implementing proper permission_callback logic that checks user capabilities and the users_can_register option, and add nonce verification and optional CAPTCHA validation to prevent automated account creation.

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. Confirm Omnishop plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for Omnishop. Note the version number. Compare to the affected range: versions up to 1.0.9 are vulnerable.
    Affected if The installed version is 1.0.9 or lower.
  2. Verify the /users/register REST endpoint exists
    Send a GET request to /wp-json/omnishop/v1/users/register or check the WP REST API schema at /wp-json/ to see if the endpoint is registered.
    Affected if The /users/register endpoint appears in the REST API routes.
  3. Test for unauthenticated user registration
    Send a POST request to /wp-json/omnishop/v1/users/register with a username, email, and password (e.g., username=testuser123, [email protected], password=TestPass123). Check if the response indicates successful account creation.
    Affected if The request succeeds and creates a new user without authentication, nonce, or CAPTCHA.
  4. Check WordPress user registration setting
    In WordPress admin, go to Settings > General and check 'Anyone can register'. Even if disabled, this CVE bypasses that check, but it provides context on the overall exposure.
    Affected if The setting is enabled (adds to exposure) or disabled (vulnerability still exploitable via this CVE).

A user is affected if the Omnishop plugin version is 1.0.9 or lower and the /users/register REST endpoint is accessible, regardless of the WordPress users_can_register setting.

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

Restrict the /users/register endpoint by implementing proper permission_callback logic that checks user capabilities and the users_can_register option, and add nonce verification and optional CAPTCHA validation to prevent automated account creation.

Recommended fix Moderate confidence

Omnishop version 1.1.0 or later

  1. 1. Update the Omnishop plugin to the latest available version (1.1.0 or higher) via WordPress admin dashboard under Plugins > Installed Plugins > Omnishop > Update Now
  2. 2. After updating, verify that the WordPress setting 'Anyone can register' (in Settings > General) is configured according to your site's requirements
  3. 3. Confirm that user registrations are being handled correctly by testing the registration flow or checking the Users list in the admin dashboard

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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