dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-3906

HIGH · 8.8 CVSS v3.1 Published 2025-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The Integração entre Eduzz e Woocommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wep_opcoes' function in all versions up to, and including, 1.7.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to edit the default registration role within the plugin's registration flow to Administrator, which allows any user to create an Administrator account.

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 Integração entre Eduzz e Woocommerce WordPress plugin lacks a capability check on the 'wep_opcoes' function, allowing any authenticated user with Subscriber-level access to modify plugin settings. Attackers can change the default registration role to Administrator, enabling creation of privileged admin accounts.

MitigationUpdate the plugin to version 1.7.6 or later which includes proper capability validation. Until patched, restrict user registration or monitor for unauthorized admin 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 if the Eduzz-WooCommerce integration plugin is installed
    Check WordPress plugins directory or admin panel for 'Integração entre Eduzz e Woocommerce' or 'Eduzz' plugin presence
    Affected if Plugin is installed and active on the WordPress site
  2. Check installed plugin version
    Inspect the plugin header in the main PHP file (usually in wp-content/plugins/eduzz-woocommerce-integration/) or view version in WordPress plugin admin panel
    Affected if Version is earlier than 1.7.6 (vulnerable) or version cannot be determined (treat as vulnerable)
  3. Confirm if user registration is enabled
    Go to WordPress Settings > General and check 'Membership: Anyone can register' checkbox, or query wp_options table for 'users_can_register' setting
    Affected if User registration is enabled on the site
  4. Inspect plugin settings for unauthorized changes
    Access plugin settings page (usually under WooCommerce or Settings) and check the default new user role setting
    Affected if Default user role has been changed to Administrator or another privileged role
  5. Audit for suspicious admin accounts
    Review WordPress users list (Users > All Users) or query wp_users and wp_usermeta tables for admin-level accounts created recently or created by unknown parties
    Affected if New administrator accounts exist that were not created by known administrators

A site is affected if the Eduzz-WooCommerce integration plugin (version before 1.7.6) is installed, user registration is enabled, and either the plugin settings show unauthorized changes or unexpected administrator accounts exist.

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 plugin to version 1.7.6 or later which includes proper capability validation. Until patched, restrict user registration or monitor for unauthorized admin account creation.

Recommended fix Moderate confidence

Version newer than 1.7.5 (check WordPress plugin repository for latest stable release)

  1. Check the current version of the 'Integração entre Eduzz e Woocommerce' plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Integração entre Eduzz e Woocommerce plugin
  4. If the installed version is 1.7.5 or lower, update the plugin to the latest available version from the WordPress plugin repository
  5. After updating, verify the 'wep_opcoes' function now includes proper capability checks (e.g., 'manage_options' check)

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