WordPress WP2LEADS plugin <= 3.5.17 - Privilege Escalation vulnerability

published 2026-11-09 5h ago modified 2026-11-09 4h ago also EUVD-2026-120148

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

Incorrect Privilege Assignment vulnerability in Tobias WP2LEADS wp2leads allows Privilege Escalation.This issue affects WP2LEADS: from n/a through 3.5.17.

Patch / fix

fixed in 1

Tobias WP2LEADS 3.5.18

Is CVE-2026-120834 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

CVSS scores

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

Affected products

Tobias WP2LEADS

Classification

Weakness

CWE-266 Incorrect Privilege Assignment

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/wp2leads/vulnerability/wordpress-wp2leads-plugin-3-5-17-privilege-escalation-vulner
vdb-entry

Sources

CVE List CVE-2026-120834
NVD CVE-2026-120834

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.