WordPress VISeek plugin <= 1.0.5 - Cross Site Request Forgery (CSRF) vulnerability

published 2026-11-11 22h ago modified 2026-11-11 20h ago also EUVD-2026-123383

cvss: 5.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

Cross-Site Request Forgery (CSRF) vulnerability in VillaTheme VISeek viseek-easy-custom-search allows Cross Site Request Forgery.This issue affects VISeek: from n/a through 1.0.5.

Patch / fix

fixed in 1

VillaTheme VISeek 1.0.6

Is CVE-2026-121770 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: no
Technical impact: partial
Assessed: 21h ago (2026-11-11)

CVSS scores

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

Affected products

VillaTheme VISeek

Classification

Weakness

CWE-352 Cross-Site Request Forgery

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/viseek-easy-custom-search/vulnerability/wordpress-viseek-plugin-1-0-5-cross-site-re
vdb-entry

Sources

CVE List CVE-2026-121770
NVD CVE-2026-121770

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.