dbcve.org
Contact ListWordPress extension · Contactlistpro

CVE-2024-34821

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 2.9.88 or later.
See remediation →
62/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
Missing Authorization vulnerability in Anssi Laitila Contact List contact-list.This issue affects Contact List: from n/a through <= 2.9.87.

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 · moderate confidence

A missing authorization vulnerability exists in the Anssi Laitila Contact List WordPress plugin (versions through 2.9.87). The flaw allows unauthenticated or unauthorized users to access functionality that should require proper authorization checks, likely exposing sensitive contact list data or enabling unauthorized actions.

MitigationApply the vendor-supplied patch/updated version immediately. Implement proper capability checks, nonce verification, and role-based access controls on all sensitive plugin functions and AJAX endpoints.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Contact ListWordPress extension
Affected:< 2.9.88

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
None

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

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. Verify Contactlistpro plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or check the wp-content/plugins/ directory for a folder containing 'contactlistpro' or similar
    Affected if The Contactlistpro plugin folder exists in the WordPress plugins directory
  2. Check installed plugin version
    In WordPress admin, find the Contact List plugin in the plugins list and read the version number displayed beneath the plugin name, or open the main plugin PHP file and look for the 'Version' header comment
    Affected if The version number is lower than 2.9.88 (e.g., 2.9.87, 2.9.86, etc.)
  3. Identify exposed AJAX endpoints
    Examine the plugin PHP files for wp_ajax_ and wp_ajax_nopriv_ action hooks. These hooks register AJAX endpoints that can be called from the browser
    Affected if The plugin registers AJAX actions that lack capability checks or nonce verification, particularly those using wp_ajax_nopriv_ (accessible to unauthenticated users)
  4. Test unauthenticated access to plugin functions
    Use a tool like Burp Suite or curl to send requests to common WordPress AJAX endpoints (admin-ajax.php) with plugin-specific action parameters, without providing authentication cookies or valid nonces
    Affected if The server returns successful responses containing contact list data or performs actions without rejecting the request for lack of authorization

If the Contactlistpro plugin is installed at version 2.9.87 or lower and its AJAX endpoints are accessible to unauthenticated users without proper authorization checks, the environment is affected by CVE-2024-34821.

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
Upgrade available Upgrade to 2.9.88 or later
Fixed in 2.9.88
Interim mitigation

Apply the vendor-supplied patch/updated version immediately. Implement proper capability checks, nonce verification, and role-based access controls on all sensitive plugin functions and AJAX endpoints.

Recommended fix High confidence

Contact List version 2.9.88

  1. Backup your WordPress site and database before performing any updates
  2. Update the Contact List plugin by Anssi Laitila to version 2.9.88
  3. After updating, verify the plugin version shows 2.9.88 in the WordPress plugins admin panel
  4. Test that contact list functionality works correctly after the update

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

Fix this in Contact List Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34821 — 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-34821 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