Skip to main content
VulnerabilityPublished Updated

CVE-2026-16746: MultiVendorX (WordPress plugin) · Insecure Direct Object Reference

Affects MultiVendorX (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.7 Low : upgrade to 5.0.11 when convenient.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 3.1 base score
2.7Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.11
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade MultiVendorX (WordPress plugin) to 5.0.11.

Affected software

ProductAffectedFixed in
MultiVendorXAffected
  • <5.0.11
Fixed in
  • 5.0.11

AI-suggested

Users should upgrade to MultiVendorX version 5.0.11 or later once available, as the vulnerability affects versions before 5.0.11. Until a fix is confirmed, restrict vendor-level user permissions and monitor access to sensitive data.

Description

The MultiVendorX WordPress plugin before 5.0.11 does not verify that the requested store belongs to the current user in one of its REST API endpoints, allowing any vendor-level user to read other vendors' commission and financial data.

References

Community reviews

Loading reviews…