WordPress WP2LEADS plugin <= 3.5.17 - Privilege Escalation vulnerability
WP2LEADS WordPress plugin versions 3.5.17 and earlier are affected. The fix is in 3.5.18, and the vendor's own rating is not given.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.5.18
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.5.18.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The WordPress WP2LEADS plugin (all versions up to and including 3.5.17) has an incorrect privilege assignment flaw that lets an attacker escalate their privileges. It can be reached remotely, without logging in, and the advisory gives no details beyond that.
Read the original description
Incorrect Privilege Assignment vulnerability in Tobias WP2LEADS wp2leads allows Privilege Escalation.This issue affects WP2LEADS: from n/a through 3.5.17.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.3/10CVSS 7.3
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.5.18.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wp2leads
through 3.5.17
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120834
Is CVE-2026-120834 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A low-privilege user can exploit this flaw to gain admin rights and full control of the site. The facts do not describe the exact mechanism.Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-120834?
wp2leads: through 3.5.17.Source: cve.now feed data
Am I affected, and how do I check?
WP2LEADS plugin versions 3.5.17 and earlier are listed as vulnerable. You can check the installed version in the WordPress admin under Plugins, where the version is shown beside WP2LEADS.Source: patchstack.com, cve.org
How do I fix CVE-2026-120834?
Update the WP2LEADS plugin to version 3.5.18 or later, the latest available version.Source: patchstack.com, cve.org