dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39701

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-08
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 Andrew ShopWP wpshopify allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ShopWP: from n/a through <= 5.2.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 ShopWP (wpshopify) WordPress plugin allows attackers to exploit incorrectly configured access control security levels. This broken access control issue likely permits unauthenticated or under-privileged users to access administrative functions that should require higher privilege levels. The vulnerability affects all versions through 5.2.4.

MitigationImplement proper capability checks (e.g., current_user_can()) on all administrative AJAX endpoints and admin pages to verify users have appropriate permissions before allowing access to sensitive operations.

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. Check installed ShopWP version
    Locate the main ShopWP plugin file (usually shopwp/free-woocommerce/includes/class-plugin.php or similar) and read the Version header from the plugin comment block. Alternatively, run `wp plugin list --filter=shopwp --format=json` if WP-CLI is available, or view the plugin in WordPress admin under Plugins > Installed Plugins.
    Affected if The installed version is lower than 5.2.5, indicating the missing authorization fix has not been applied.
  2. Verify ShopWP plugin is active
    Confirm the ShopWP plugin is currently activated on the WordPress site. Check via WP-CLI: `wp plugin status shopwp` or through WordPress admin dashboard Plugins page.
    Affected if The plugin is active and the version is below 5.2.5, meaning the vulnerable code is running.
  3. Inspect REST API endpoints for ShopWP
    Send a GET request to the WordPress REST API routes: `GET /wp-json/` and look for routes under the `shopwp/v1` namespace. Test sensitive endpoints (such as those handling orders, products, or customer data) using a low-privilege or unauthenticated request.
    Affected if REST API endpoints under the ShopWP namespace respond with sensitive data or perform actions without requiring authentication or proper capability checks.
  4. Inspect admin-ajax.php for exposed actions
    Review the ShopWP plugin source code for registered AJAX actions (search for `add_action('wp_ajax_` and `add_action('wp_ajax_nopriv_` calls). Test these AJAX endpoints with unauthenticated or low-privilege requests to see if sensitive operations are accessible.
    Affected if AJAX actions are registered with `nopriv` capability and perform sensitive operations without verifying user capabilities.
  5. Check for missing capability checks in plugin code
    Examine the main ShopWP plugin PHP files for function calls that handle sensitive operations (order retrieval, product management, customer data). Look for presence of functions like `current_user_can`, `wp_verify_nonce`, or capability checks before executing sensitive logic.
    Affected if Sensitive functionality lacks capability verification or nonce validation checks, indicating the authorization vulnerability exists.

You are affected if ShopWP is active and the installed version is below 5.2.5, or if sensitive endpoints respond without proper authentication or capability verification.

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

Implement proper capability checks (e.g., current_user_can()) on all administrative AJAX endpoints and admin pages to verify users have appropriate permissions before allowing access to sensitive operations.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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