Unauthenticated message disclosure via unchecked request handler
Published Oct 25, 2024 · Updated Apr 8, 2026
Missing authorization in WPS Telegram Chat 4.6.0 and earlier allows remote attackers to read messages sent through the Telegram Bot API. The public request handler in wps-telegram-chat-public-handler.php retrieves Telegram updates without performing a WordPress capability check. No WordPress account or user interaction is required, and exposure is limited to messages available through the configured bot.
Summary
What happened
Missing authorization in WPS Telegram Chat 4.6.0 and earlier allows remote attackers to read messages sent through the Telegram Bot API. The public request handler in wps-telegram-chat-public-handler.php retrieves Telegram updates without performing a WordPress capability check. No WordPress account or user interaction is required, and exposure is limited to messages available through the configured bot.
The record
- CVE
- CVE-2024-9630
- Published
- Oct 25, 2024
- Updated
- Apr 8, 2026
- Vendor
- WPSolutions
- Product
- WPS Telegram Chat
- Classifications
- CWE-862, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 25, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.6.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo