dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-31773

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-01
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
Missing Authorization vulnerability in cedcommerce Ship Per Product ship-per-product allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Ship Per Product: from n/a through <= 2.1.0.

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 cedcommerce's Ship Per Product WooCommerce plugin allows users to access functionality that should be constrained by access control lists (ACLs). The vulnerability stems from insufficient permission checks on certain administrative functions, potentially enabling unauthenticated or low-privilege users to modify shipping configurations or access sensitive shipping data.

MitigationUpdate Ship Per Product to the latest version beyond 2.1.0. If no patch is available, implement server-side capability checks using WordPress/WooCommerce authorization functions (e.g., current_user_can) on all shipping configuration endpoints and restrict admin AJAX actions to authenticated users with proper roles.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Ship Per Product plugin is installed
    Navigate to WordPress admin > Plugins and confirm 'Ship Per Product WooCommerce' by cedcommerce is listed as an active or inactive plugin
    Affected if The plugin appears in the installed plugins list regardless of activation status
  2. Identify installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view the version details, or inspect the main plugin file (typically in /wp-content/plugins/ship-per-product-woocommerce/ and look for the 'Version:' header in the plugin comments)
    Affected if The installed version is 2.1.0 or lower (versions up to and including 2.1.0 lack proper authorization checks)
  3. Inspect admin AJAX endpoints for authorization gaps
    Examine the plugin's PHP files for 'add_action("wp_ajax_' calls that lack 'current_user_can' or similar capability verification before executing sensitive shipping configuration changes
    Affected if AJAX action handlers exist without preceding capability checks allowing low-privilege or unauthenticated access
  4. Check for exposed shipping configuration endpoints
    Review plugin PHP files for any direct HTTP request handlers (functions hooked to 'init', 'admin_init', or REST API routes) that modify shipping settings without verifying user roles or capabilities
    Affected if Administrative functions that modify shipping configurations can be triggered without proper ACL validation
  5. Audit user role assignments to the shipping plugin
    In WordPress admin > Users, review which user roles have access to shipping-related settings, checking if low-privilege users (e.g., Shop Manager) can access shipping configuration pages
    Affected if Users with insufficient privileges can access or modify shipping configurations that should be restricted to Administrators only

The environment is affected if the Ship Per Product WooCommerce plugin is installed at version 2.1.0 or lower, or if admin AJAX endpoints lack capability checks allowing unauthorized access to shipping configuration functions.

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 Ship Per Product to the latest version beyond 2.1.0. If no patch is available, implement server-side capability checks using WordPress/WooCommerce authorization functions (e.g., current_user_can) on all shipping configuration endpoints and restrict admin AJAX actions to authenticated users with proper roles.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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