VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

REST API TO MiniProgram <= 5.1.2 — Authenticated (Subscriber+) Insecure Direct Object Reference via 'userid' REST API Parameter

CVE-2026-3460Published · Updated

Action summary

Affected: ≤5.1.2No patch available

What to do until a fix ships
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-20 Improper Input Validation
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

REST API TO MiniProgram rest-api-to-miniprogram

  1. Affected≤ 5.1.2
  2. PatchedNo fix yet

No patched version available.

You are affected if you run ≤ 5.1.2. No fixed version has been released.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under REST API TO MiniProgram.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch REST API TO MiniProgram to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Ronnachai Sretawat Na Ayutaya (Simonhaskelly), Ronnachai Chaipha (rxnr).

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in REST API TO MiniProgram

All 5
More vulnerabilities in REST API TO MiniProgram
SeverityVulnerabilityCVEPublished
Medium4.3Cross-Site Request Forgery
≤4.7.1No patch available
CVE-2025-28886
Critical9.8Unauthenticated Arbitrary User Email Update and Privilege Escalation via Account Takeover
≤4.7.1Update to 4.7.6
CVE-2024-8485
High7.5Unauthenticated SQL Injection
≤4.7.1Update to 5.1
CVE-2024-8484
Medium6.4Authenticated (Subscriber+) Media Attachment Deletion
≤4.7.7No patch available
CVE-2023-0551

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?