dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-9629

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 Contact Form 7 + Telegram plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on the 'wpcf7_Telegram::ajax' function in versions up to, and including, 0.8.5. This makes it possible for authenticated attackers, with subscriber-level access and above, to approve, pause and refuse subscriptions.

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 Contact Form 7 + Telegram WordPress plugin lacks proper capability validation on its ajax handler function (wpcf7_Telegram::ajax). This allows any authenticated user with subscriber-level permissions to modify subscription settings (approve, pause, refuse) by making direct AJAX calls to the vulnerable endpoint, bypassing intended access controls.

MitigationUpdate the plugin to the latest patched version. If no patch is available, disable the plugin or add capability checks (current_user_can) to the ajax function and implement nonce verification for all subscription management actions.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify plugin installation
    Navigate to WordPress admin Plugins page and confirm 'Contact Form 7 + Telegram' is installed and active
    Affected if Plugin is installed and active
  2. Identify plugin version
    Click 'View Details' on the plugin in the WordPress plugins list to display the installed version number, then compare against any known affected version ranges
    Affected if Installed version falls within known vulnerable version range (if published)
  3. Enumerate subscriber-level accounts
    In WordPress admin, go to Users > All Users and filter or check for users with 'Subscriber' role
    Affected if At least one user with subscriber role exists in the system
  4. Check ajax handler capability validation
    Access the plugin source files and locate the wpcf7_Telegram::ajax function in the main plugin file. Verify if the function includes current_user_can checks before processing subscription settings
    Affected if The ajax function lacks capability validation checks (current_user_can) and is accessible without proper authorization
  5. Test ajax endpoint accessibility
    With a subscriber-level test account, attempt a POST request to wp-admin/admin-ajax.php with action=wpcf7_Telegram and subscription modification parameters
    Affected if Request succeeds and modifies subscription settings without permission error

A user is affected if the Contact Form 7 + Telegram plugin is active, subscriber accounts exist, and the wpcf7_Telegram ajax handler lacks capability validation, allowing unauthorized subscription changes.

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 plugin to the latest patched version. If no patch is available, disable the plugin or add capability checks (current_user_can) to the ajax function and implement nonce verification for all subscription management actions.

Recommended fix Moderate confidence

Latest version newer than 0.8.5

  1. Update the Contact Form 7 + Telegram plugin to the latest available version (newer than 0.8.5)
  2. Verify the update was applied successfully in the WordPress plugins dashboard
  3. Confirm that subscriber-level users can no longer modify subscriptions without proper authorization

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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