dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-9821

HIGH · 8.8 CVSS v3.1 Published 2024-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the 'stm_wpcfto_get_settings' AJAX action in all versions up to, and including, 1.2.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to view the Telegram Bot Token, a secret token used to control the bot, which can then be used to log in as any existing user on the site, such as an administrator, if they know the username, due to the Login with Telegram feature.

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 Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to an IDOR/insecure direct object reference issue. The 'stm_wpcfto_get_settings' AJAX action lacks proper capability checks, allowing any authenticated user with subscriber-level privileges to retrieve sensitive settings including the Telegram Bot Token by exploiting the insecure AJAX endpoint.

MitigationUpdate the plugin to version 1.2.8 or later which includes proper authorization checks. Alternatively, disable the Telegram login feature and rotate any exposed bot tokens immediately.

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
High
Integrity
High
Availability
High

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

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 plugin installation and version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Bot for Telegram on WooCommerce' and note the version number displayed
    Affected if The installed version is lower than 1.2.8
  2. Verify AJAX endpoint accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=stm_wpcfto_get_settings while authenticated as a subscriber-level user
    Affected if The endpoint returns sensitive settings (including Telegram Bot Token) without requiring elevated privileges
  3. Check for subscriber-level accounts
    Navigate to Users > All Users in WordPress admin and review user roles
    Affected if Any subscriber-level user accounts exist in the system
  4. Test unauthorized settings retrieval
    Using a low-privileged user account, invoke the AJAX action and inspect the response for sensitive configuration data
    Affected if The response contains bot tokens, API keys, or other sensitive settings that should be restricted to administrators

You are affected if the plugin version is below 1.2.8 and the stm_wpcfto_get_settings AJAX endpoint is accessible to subscriber-level users, allowing them to retrieve sensitive settings.

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 version 1.2.8 or later which includes proper authorization checks. Alternatively, disable the Telegram login feature and rotate any exposed bot tokens immediately.

Recommended fix Moderate confidence

Latest version after 1.2.7 (check wordpress.org for current release)

  1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  2. Locate 'Bot for Telegram on WooCommerce' in the plugin list
  3. Check if an update is available and update to the latest version
  4. Alternatively, download the latest version from wordpress.org/plugins/bot-for-telegram-on-woocommerce/ and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the Telegram Bot Token is no longer exposed by testing the stm_wpcfto_get_settings AJAX action with a subscriber-level account

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-9821 — 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-9821 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