WordPress security by component
LeadConnector
Plugin description
LeadConnector is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Mar 26, 2026; the highest CVE/CNA score is 8.6.
Plugin slug:
leadconnectorLatest vulnerability
CVE-2026-1890: LeadConnector: A security weakness
LeadConnector is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 3.0.22.
| Safe version |
|
||
|---|---|---|---|
| Mar 26, 2026 |
CVE-2026-1890
LeadConnector: A security weakness
LeadConnector is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 3.0.22.
|
3.0.22 |
CVE5.3
NVDPending
|
| Feb 19, 2026 |
CVE-2026-25441
LeadConnector: A security weakness
LeadConnector is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Mar 27, 2025 |
CVE-2025-30893
LeadConnector: Cross-site scripting
LeadConnector is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVDPending
|
| May 06, 2024 |
CVE-2024-34378
LeadConnector: A security weakness
LeadConnector is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE8.6
NVDPending
|
| Apr 30, 2024 |
CVE-2024-1371
LeadConnector: A security weakness
LeadConnector is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE6.5
NVDPending
|