dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-3460

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-21
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
The REST API TO MiniProgram plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.2. This is due to the permission callback (update_user_wechatshop_info_permissions_check) only validating that the supplied 'openid' parameter corresponds to an existing WordPress user, while the callback function (update_user_wechatshop_info) uses a separate, attacker-controlled 'userid' parameter to determine which user's metadata gets modified, with no verification that the 'openid' and 'userid' belong to the same user. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify arbitrary users' store-related metadata (storeinfo, storeappid, storename) via the 'userid' REST API parameter.

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 REST API TO MiniProgram WordPress plugin has an IDOR vulnerability where the permission callback validates the 'openid' parameter but the actual callback function uses a separate attacker-controlled 'userid' parameter without verifying both belong to the same user. This allows authenticated subscribers to modify arbitrary users' store metadata (storeinfo, storeappid, storename).

MitigationUpdate the plugin to a patched version once available, or implement proper authorization checks verifying that the 'userid' corresponds to the authenticated user before modifying metadata.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm plugin installation
    Check if the REST API TO MiniProgram plugin is installed in WordPress by looking in wp-content/plugins/ for a folder named 'rest-api-to-miniprogram' or similar, or via WordPress admin panel under Plugins
    Affected if The plugin is installed and active
  2. Identify plugin version
    Check the plugin version in the plugin's main PHP file header (usually in the plugin folder root, look for 'Version:' comment) or in WordPress admin under Plugins > Installed Plugins
    Affected if The installed version matches or precedes the vulnerable version range (verify against official vulnerability disclosure)
  3. Verify REST API endpoint accessibility
    Test if the plugin's REST API endpoints are publicly accessible by making a GET request to endpoints like /wp-json/miniprogram/v1/ or similar paths exposed by the plugin
    Affected if The REST API endpoints respond and are not restricted by additional authentication layers
  4. Check user role configuration
    In WordPress admin, navigate to Users > Subscribers and verify that the 'subscriber' role exists and has API access permissions, or check if any subscriber-level accounts exist on the site
    Affected if Subscriber-level users exist with API access privileges
  5. Test parameter behavior (if safe to do so)
    With a low-privilege subscriber account, attempt to send a crafted request to the affected endpoint with mismatched 'openid' and 'userid' parameters to observe if authorization is properly enforced
    Affected if The API accepts a 'userid' parameter that differs from the authenticated user's identity without proper ownership verification

A user is affected if the REST API TO MiniProgram plugin is installed and active, the vulnerable endpoint is accessible, and subscriber-level accounts can manipulate store metadata belonging to other users via mismatched openid/userid parameters.

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 a patched version once available, or implement proper authorization checks verifying that the 'userid' corresponds to the authenticated user before modifying metadata.

Recommended fix Moderate confidence

Latest version higher than 5.1.2 (check WordPress plugin repository for current stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'REST API TO MiniProgram' plugin
  4. 4. Check if an update is available (version higher than 5.1.2)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. After updating, verify the plugin is functioning correctly
  7. 7. Confirm the permission callback now properly validates that 'openid' and 'userid' belong to the same user

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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