dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-30772

HIGH · 8.8 CVSS v3.1 Published 2025-03-27
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
Missing Authorization vulnerability in WPClever WPC Smart Upsell Funnel for WooCommerce wpc-smart-upsell-funnel allows Privilege Escalation.This issue affects WPC Smart Upsell Funnel for WooCommerce: from n/a through <= 3.0.4.

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 WPC Smart Upsell Funnel plugin for WooCommerce allows authenticated users to perform actions outside their intended privilege level, enabling privilege escalation through improper access control checks.

MitigationUpdate to the latest version of WPC Smart Upsell Funnel for WooCommerce to obtain the vendor patch that adds proper authorization checks; review user roles and capabilities as a precautionary measure.

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. Confirm WPC Smart Upsell Funnel plugin is installed
    Navigate to WordPress admin > Plugins and locate 'WPC Smart Upsell Funnel for WooCommerce' in the installed plugins list
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    Click on the plugin in the WordPress plugins list to view its details, or check the plugin header in /wp-content/plugins/wpc-smart-upsell-funnel/ via file manager or FTP
    Affected if The version displayed is lower than the patched version released by the vendor (the specific fixed version number should be obtained from the vendor advisory)
  3. Verify WooCommerce is active
    Navigate to WordPress admin > Plugins and confirm WooCommerce is installed and activated, as this plugin is dependent on WooCommerce
    Affected if WooCommerce is active and the vulnerable plugin is installed
  4. Review user accounts and roles
    Navigate to WordPress admin > Users and examine all user accounts. Check if any users with roles below Administrator (such as Editor, Author, Contributor, or Subscriber) have unexpected administrative capabilities or have modified their user metadata
    Affected if Lower-privileged users have been granted elevated capabilities or have modified their user roles without admin action
  5. Audit plugin capabilities and actions
    Check the WPC Smart Upsell Funnel plugin settings and review any logged actions or capability changes. Examine server access logs for POST requests to /wp-admin/admin-ajax.php or plugin admin pages made by non-administrator accounts
    Affected if Non-administrator users are able to access or modify plugin settings or perform actions that should require administrator privileges

A user is affected if the WPC Smart Upsell Funnel plugin for WooCommerce is installed and active, with a version that predates the vendor's authorization patch, and any lower-privileged authenticated users exist on the site who could potentially escalate their privileges through the 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 to the latest version of WPC Smart Upsell Funnel for WooCommerce to obtain the vendor patch that adds proper authorization checks; review user roles and capabilities as a precautionary measure.

Recommended fix Moderate confidence

Upgrade to WPC Smart Upsell Funnel for WooCommerce version 3.0.5 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WPC Smart Upsell Funnel for WooCommerce' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest patched version
  5. 5. Alternatively, download the latest version from the official WordPress plugin repository or WPClever website
  6. 6. After updating, verify the version number reflects the latest release
  7. 7. Test the plugin functionality to ensure the update does not break existing workflows
Caveat Review plugin changelog before upgrading; test in staging environment first

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 / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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