WordPress Do Lasso plugin <= 358 - Insecure Direct Object References (IDOR) vulnerability

published 2026-08-13 2mo ago modified 2026-10-23 17d ago also EUVD-2026-57948

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits: 0; none known

Unauthenticated Insecure Direct Object References (IDOR) in Do Lasso <= 358 versions.

Is CVE-2026-28155 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 2mo ago (2026-08-13)

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Affected products

Lasso Analytics, Inc. Do Lasso

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/lasso/vulnerability/wordpress-do-lasso-plugin-358-insecure-direct-object-references
vdb-entry

Sources

CVE List CVE-2026-28155
NVD CVE-2026-28155

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.