Skip to main content
VulnerabilityPublished Updated

CVE-2024-1371: LeadConnector (WordPress plugin) · Missing Authorization

Affects LeadConnector (WordPress plugin)Source CVE Database V5

0

Mentioned vulnerabilities

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
varunvairavanlc LeadConnectorAffected
  • =0
Fixed in–

AI-suggested

Until an official fix is released, consider restricting access to the affected API endpoint or disabling the LeadConnector plugin if feasible. Monitor vendor channels for updates and apply patches promptly once available.

Description

The LeadConnector plugin for WordPress is vulnerable to unauthorized modification & loss of data due to a missing capability check on the lc_public_api_proxy() function in all versions up to, and including, 1.7. This makes it possible for unauthenticated attackers to delete arbitrary posts. CVE-2024-34378 is likely a duplicate of this issue.

References

Community reviews

Loading reviews…