LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3460: REST API TO MiniProgram <= 5.1.2 - Authenticated (Subscriber+) Insecure Direct Object Reference via 'userid' REST API Parameter

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.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-3460 affects the WordPress plugin REST API TO MiniProgram through version 5.1.2. A logged-in low-privilege user may be able to change store-related metadata for other users. This is an integrity issue, not a data theft or full site takeover finding based on the provided sources.

Executive priority

Treat as a medium-priority integrity risk. Prioritize internet-facing WordPress sites where customers, partners, or unknown users can create accounts. Remediate during the next security maintenance cycle unless the plugin supports critical commerce or store workflows.

Technical view

The plugin’s REST permission check validates that an 'openid' maps to an existing WordPress user, but the update handler uses a separate attacker-controlled 'userid' to select whose metadata is modified. Sources identify affected metadata as storeinfo, storeappid, and storename. The issue is described as authenticated Subscriber+ IDOR.

Likely exposure

Exposure is limited to WordPress sites running REST API TO MiniProgram version 5.1.2 or earlier, especially sites allowing untrusted users to authenticate as Subscribers or higher. Sites without this plugin are not affected.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires an authenticated user according to the description, despite the bundled CVSS vector showing PR:N, which appears inconsistent with the narrative.

Researcher notes

The key control failure is object binding: authorization validates one user identifier but the state change targets another. Code references in WordPress Trac are provided for the permission callback and update path. Fix availability is not established in the provided sources.

Mitigation direction

  • Inventory WordPress sites for REST API TO MiniProgram installations.
  • Identify plugin versions at or below 5.1.2.
  • Check vendor or WordPress plugin guidance for a fixed release.
  • Update if a fixed version is available from trusted sources.
  • Disable the plugin if unused or no fix is available.
  • Review whether public user registration is necessary.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record the installed plugin version.
  • Review user roles for untrusted Subscriber-level accounts.
  • Inspect store-related user metadata for unexpected changes.
  • Monitor relevant WordPress REST activity for suspicious authenticated updates.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3460 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-3460Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
xjbREST API TO MiniProgram0unaffected
Weakness

CWE details

CWE-20

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs