dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-3853

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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 WPshop 2 – E-Commerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions 2.0.0 to 2.6.0 via the callback_generate_api_key() due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create valid API keys on behalf of other users.

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 WPshop 2 E-Commerce plugin for WordPress is vulnerable to Insecure Direct Object Reference (IDOR) in versions 2.0.0 through 2.6.0. The callback_generate_api_key() function lacks validation on user-controlled key parameters, allowing authenticated attackers with Subscriber-level access to create valid API keys on behalf of other users.

MitigationUpdate to the latest patched version of WPshop 2. If no patch is available, disable the plugin or implement role-based access restrictions as a temporary measure until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify WPshop 2 plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'WPshop 2 E-Commerce' (or wpshop2) and note the version number displayed. Alternatively, inspect the plugin main file header via file system access.
    Affected if The plugin is installed and the version falls between 2.0.0 and 2.6.0 inclusive.
  2. Verify the API key generation functionality exists
    Inspect the plugin files for the callback_generate_api_key() function. In a standard WordPress plugin structure, this may be found in includes/api.php, class-wpshop-api.php, or similar within the plugin directory. Search the codebase for the function definition.
    Affected if The function callback_generate_api_key() exists in the plugin code, indicating the vulnerable feature is present.
  3. Confirm API endpoints are accessible
    Test whether the API key generation endpoint is reachable. In a default WPshop 2 setup, this typically involves a REST API route or an admin ajax handler. Attempt a request to the relevant endpoint (commonly /wp-json/wpshop/v1/ or wp-admin/admin-ajax.php?action=wpshop_generate_api_key) using a low-privilege account.
    Affected if The API key generation endpoint responds without requiring administrator-level privileges, indicating the IDOR attack surface is exposed.
  4. Audit existing user accounts and roles
    In WordPress admin, go to Users > All Users. Review the list to identify any users assigned the Subscriber role. Also check Users > Add New to see if Subscriber role is available for registration if user registration is enabled in Settings > General.
    Affected if Subscriber-level accounts exist or can be created, providing an attacker with the minimum required access to exploit the IDOR vulnerability.
  5. Review API keys for unauthorized creation
    If WPshop 2 provides an API key management interface (typically under WPshop > Settings > API or similar), inspect the list of generated API keys. Cross-reference creation dates and associated user IDs against known administrator actions.
    Affected if API keys exist that were not created by the account owner or that associate a Subscriber user with an API key they did not explicitly generate, indicating potential exploitation.

The environment is affected if WPshop 2 E-Commerce plugin version 2.0.0-2.6.0 is installed, the API key generation feature is present and accessible, and Subscriber-level users can access the system.

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 to the latest patched version of WPshop 2. If no patch is available, disable the plugin or implement role-based access restrictions as a temporary measure until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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