CVE-2024-9627

TeploBot - Telegram Bot for WP <= 1.3 - Telegram Bot Token Disclosure

2024-10-21 00:00
István Márton

Strategic Overview

Status
Unpatched
Affected Version
<= 1.3
CVSS
8.6High
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-9627
View all TeploBot – Telegram Bot for WP vulnerabilities

At a glance

CVE-2024-9627 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the TeploBot WordPress plugin, affecting versions <= 1.3. It carries a CVSS score of 8.6 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2024, reported by István Márton.

Vulnerability Overview

The TeploBot - Telegram Bot for WP plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the 'service_process' function in all versions up to, and including, 1.3. This makes it possible for unauthenticated attackers to view the Telegram Bot Token, which is a secret token to control the bot.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

TeploBot <= 1.3 carries this weakness at service_process, and reaching it takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. No fixed build of this plugin is recorded for TeploBot yet, so installs running <= 1.3 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

No patched version is recorded yet, so there is nothing to update to; WordSec's vulnerability alerts flag this record the moment that changes.

  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C