Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-9627: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in gsuvorov TeploBot – Telegram Bot for WP

0
High
VulnerabilityCVE-2024-9627cvecve-2024-9627cwe-200
Published: Tue Oct 22 2024 (10/22/2024, 06:50:30 UTC)
Source: CVE Database V5
Vendor/Project: gsuvorov
Product: TeploBot – Telegram Bot for WP

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/09/2026, 20:38:28 UTC

Technical Analysis

CVE-2024-9627 is a vulnerability in the TeploBot – Telegram Bot for WP plugin for WordPress, affecting all versions up to and including 1.3. The issue arises from missing authorization checks on the 'service_process' function, which allows unauthenticated attackers to retrieve the Telegram Bot Token. This token is a sensitive secret that controls the Telegram bot, and its exposure constitutes an information disclosure vulnerability classified under CWE-200. The vulnerability has a CVSS 3.1 base score of 8.6, indicating high severity due to network attack vector, no required privileges or user interaction, and high confidentiality impact.

Potential Impact

An attacker can obtain the Telegram Bot Token without authentication, potentially allowing unauthorized control or manipulation of the Telegram bot associated with the WordPress site. This could lead to further malicious activities leveraging the bot. The confidentiality impact is high, while integrity and availability impacts are lower but present. No known exploits in the wild have been reported at this time.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the affected plugin's endpoints and monitor for unusual activity involving the Telegram Bot Token. Consider disabling the plugin if possible to prevent exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-10-08T13:01:26.181Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6b54b7ef31ef0b55243d

Added to database: 2/25/2026, 9:36:20 PM

Last enriched: 4/9/2026, 8:38:28 PM

Last updated: 4/12/2026, 4:24:07 AM

Views: 18

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses