WordPress Sumo plugin <= 1.34 - Cross Site Request Forgery (CSRF) vulnerability

published 2024-04-12 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-29161

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

Cross-Site Request Forgery (CSRF) vulnerability in SumoMe Sumo.This issue affects Sumo: from n/a through 1.34.

Patch / fix

fixed in 1

SumoMe Sumo 1.35

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 y ago (2024-04-17)

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected products

SumoMe Sumo

Classification

Weakness

CWE-352 Cross-Site Request Forgery

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/vulnerability/sumome/wordpress-sumo-plugin-1-34-cross-site-request-forgery-csrf-vulnerability?_s_id=
vdb-entry

Sources

CVE List CVE-2024-31265
NVD CVE-2024-31265

Fencer Vulns 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.

Summary