CVE-2024-9821
A public proof of concept exists; no exploitation attested.
- Published2024-10-12
- WeaknessCWE-200
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2024-10-1203:15CVE publishedNVD
Versions per branch
CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.2 | ≤ 1.2.4 | no fix published | CISA-ADP |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As Wordfence, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- guruteam Bot for Telegram on WooCommerceother versions: not affectedAffected
- ≤ 1.2.7no fix statedsemver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-04-08
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-11-01 01:02 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHub1 repository, unverifiedknown since 2026-11-01RandomRobbieBF/CVE-2024-9821
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2024-10-15
- CNACVSS 3.18.8known since 2026-10-23
- CNAweakness (CWE)CWE-200known since 2026-10-23
- FIRST EPSSEPSS score1.2 %2026-11-18
- PoC-in-GitHubproof of concept1known since 2026-11-01
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2024-50143same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-cfvh-mr6h-3g8qsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2024-10-12
- Last Modified
- 2026-06-17
- NVD status
- Deferred
- GitHub Advisory
- GHSA-cfvh-mr6h-3g8q
Frequently asked questions
What is CVE-2024-9821?
Is CVE-2024-9821 actively exploited?
What is the CVSS score for CVE-2024-9821?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-cfvh-mr6h-3g8q
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0