dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1371

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LeadConnector WordPress plugin has a broken access control vulnerability in the lc_public_api_proxy() function. The function lacks a capability check, allowing unauthenticated attackers to delete arbitrary posts on the WordPress site. This is a critical security flaw as it requires no authentication and can lead to data loss.

MitigationUpdate the LeadConnector plugin to version 1.8 or later, which includes proper capability checks on the lc_public_api_proxy() function. Until update is applied, consider disabling the plugin or implementing WAF rules to block malicious deletion requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm LeadConnector plugin is installed
    Navigate to WordPress admin > Plugins and look for 'LeadConnector' or 'LeadConnector - WordPress Plugin' in the installed plugins list. Note whether it is active or inactive.
    Affected if The plugin is installed and active.
  2. Identify the installed plugin version
    Click on the plugin name in the Plugins list to view its details, or check the plugin header in /wp-content/plugins/leadconnector/leadconnector.php for the 'Version' comment. Compare this version number to the fixed version 1.8.
    Affected if The installed version is earlier than 1.8 (e.g., 1.7.x, 1.6.x, etc.).
  3. Verify the vulnerable function exists
    Access the site via FTP or file manager and locate the file containing lc_public_api_proxy() in the plugin directory (typically /wp-content/plugins/leadconnector/includes/). Open the file and search for the function definition. Examine whether it includes a capability check (look for functions like current_user_can(), check_admin_referer(), or similar authorization logic).
    Affected if The lc_public_api_proxy() function exists and lacks any current_user_can() or equivalent capability check before executing its logic.
  4. Test unauthenticated access to the API proxy endpoint
    Using a tool like curl or Burp Suite, send a request to the plugin's AJAX endpoint or API proxy route that invokes lc_public_api_proxy() without providing any authentication credentials or cookies. Example: curl -X POST http://your-site.com/wp-admin/admin-ajax.php -d 'action=lc_public_api_proxy&...'. Observe whether the request is processed without being rejected.
    Affected if The request is processed without authentication, indicating the function is accessible to unauthenticated users.

You are affected if the LeadConnector plugin is installed with a version earlier than 1.8 AND the lc_public_api_proxy() function lacks capability checks, allowing unauthenticated post deletion.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the LeadConnector plugin to version 1.8 or later, which includes proper capability checks on the lc_public_api_proxy() function. Until update is applied, consider disabling the plugin or implementing WAF rules to block malicious deletion requests.

Recommended fix High confidence

LeadConnector version 1.8 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the LeadConnector plugin
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Verify the update completes successfully
  6. 6. Confirm the running version is 1.8 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1371 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data