CVE-2026-3460
Received Received - Intake
Insecure Direct Object Reference in WordPress MiniProgram Plugin Allows Metadata Modification

Publication date: 2026-03-21

Last updated on: 2026-03-21

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-21
Last Modified
2026-03-21
Generated
2026-05-07
AI Q&A
2026-03-21
EPSS Evaluated
2026-05-05
NVD
CVE-2026-3460
EUVD
EUVD-2026-14186
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wordfence rest-api-to-miniprogram 5.1.2
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The REST API TO MiniProgram plugin for WordPress has a vulnerability called Insecure Direct Object Reference (IDOR) in all versions up to 5.1.2. This happens because the permission check only verifies that the 'openid' parameter corresponds to an existing WordPress user, but the actual update function uses a separate 'userid' parameter to decide which user's metadata to modify. There is no check to ensure that the 'openid' and 'userid' belong to the same user.

As a result, an authenticated attacker with Subscriber-level access or higher can modify arbitrary users' store-related metadata such as storeinfo, storeappid, and storename by manipulating the 'userid' parameter in the REST API.


How can this vulnerability impact me? :

This vulnerability allows an attacker with at least Subscriber-level access to modify store-related metadata of any user on the WordPress site. This could lead to unauthorized changes in user data, potentially causing data integrity issues, confusion, or misuse of store information.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart