Unauthenticated Store Access in MultiVendorX WordPress Plugin

The MultiVendorX WordPress plugin before 5.0.11 does not verify that the store targeted through its REST API belongs to the requesting vendor, allowing an authenticated vendor (Store Owner and above) to view, take over, permanently delete, or modify any other vendor's store on the marketplace.

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-16605 represents a critical authorization bypass vulnerability in the MultiVendorX WordPress plugin affecting multi-vendor marketplaces. The plugin fails to validate that REST API requests from authenticated vendors only access their own store data, allowing any authenticated vendor with Store Owner privileges or above to view, modify, delete, or take over competing vendors' stores. This vulnerability is particularly dangerous because it requires only basic authentication—no additional exploit complexity—making it accessible to any marketplace participant with legitimate account credentials. Affected organizations include WordPress-based multi-vendor marketplaces, marketplace operators, and vendors relying on the plugin for data isolation and store security.

Casky's 283 mapped security skills detect this vulnerability pattern by analyzing authorization flaws mapped to MITRE ATT&CK TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using Casky would identify suspicious findings such as: unauthorized data access attempts across store boundaries in API logs, privilege escalation indicators where vendor accounts request resources outside their assigned scope, and lateral movement patterns where authenticated sessions access multiple store configurations. The extended reasoning capabilities would correlate REST API calls lacking proper store ownership validation with TA0004 techniques, while flagging the weak authentication context (authenticated but not authorized) against TA0006 patterns. Security teams would see anomalies in API request patterns indicating vendors querying or modifying store_id parameters that don't match their own account associations—the classic signature of missing object-level access controls.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-16605.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

cryptography · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-16605

Casky has 283 skills that investigate the attack patterns behind CVE-2026-16605. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn