dbcve.org
Order Notification For TelegramWordPress extension · Choplugins

CVE-2024-9686

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-25
Fix available
A fix is available. Upgrade to after 1.0.1 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
The Order Notification for Telegram plugin for WordPress is vulnerable to unauthorized test message sending due to a missing capability check on the 'nktgnfw_send_test_message' function in versions up to, and including, 1.0.1. This makes it possible for unauthenticated attackers to send a test message via the Telegram Bot API to the user configured in the settings.

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

This is a broken access control vulnerability (CWE-862) in the Order Notification for Telegram WordPress plugin. The 'nktgnfw_send_test_message' function lacks a WordPress capability check, allowing any unauthenticated user to trigger it and send test messages through the configured Telegram Bot API to the plugin settings.

MitigationUpdate the plugin to version 1.0.2 or later which includes proper capability checks. If no update is available, disable the plugin until a patched version is released.

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
Order Notification For TelegramWordPress extension
Affected:<= 1.0.1

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. Identify if the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Order Notification for Telegram' or 'Choplugins Order Notification For Telegram'. Alternatively, check the plugin directory at wp-content/plugins/ for a folder containing 'telegram' and 'order-notification' or similar naming.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin Plugins page, click on the plugin name to view details, or inspect the main plugin PHP file header for the 'Version' tag. Compare against the affected range: <= 1.0.1.
    Affected if The installed version is 1.0.1 or lower
  3. Verify unauthenticated access to the vulnerable function
    Check if the WordPress site responds to a direct POST request to admin-ajax.php with action=nktgnfw_send_test_message without requiring authentication. Use a tool like curl: curl -X POST https://your-site.com/wp-admin/admin-ajax.php -d 'action=nktgnfw_send_test_message'
    Affected if The request returns a valid response (not a 401/403 authentication error) indicating the function is accessible without login
  4. Confirm Telegram Bot configuration exists
    Navigate to the plugin settings page in WordPress admin (usually under Settings > Order Notification for Telegram) and check if a Telegram Bot Token and Chat ID are configured in the plugin settings.
    Affected if A Telegram Bot API token and chat ID are saved in the plugin configuration, meaning messages could be sent if the vulnerability is exploited

The environment is affected if the Order Notification for Telegram plugin version 1.0.1 or lower is installed and the vulnerable AJAX endpoint is accessible without authentication, regardless of whether Telegram credentials are configured.

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 a release after 1.0.1
Interim mitigation

Update the plugin to version 1.0.2 or later which includes proper capability checks. If no update is available, disable the plugin until a patched version is released.

Recommended fix Moderate confidence

Latest available version of Order Notification for Telegram (verify version > 1.0.1)

  1. Check WordPress plugin repository for the latest version of 'Order Notification for Telegram' plugin
  2. If a version newer than 1.0.1 is available, navigate to Plugins > All Plugins in WordPress admin dashboard
  3. Deactivate and delete the current 'Order Notification for Telegram' plugin
  4. Install the newer version from the WordPress plugin repository or upload the new version
  5. Reactivate the plugin and verify the Telegram notification settings are intact
  6. If no newer version exists, consider using an alternative plugin with similar functionality that receives regular security updates

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

Fix this in Order Notification For Telegram Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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