Channel
@cve_mitre_org
On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
1,301subscribers
+35 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001482144243 |
|---|---|
| Type | Channel |
| Username | @cve_mitre_org |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/cve_mitre_org |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 20:54 | 1,301 | +4 |
| 29 Aug 2026, 13:35 | 1,297 | +14 |
| 23 Aug 2026, 23:18 | 1,283 | +10 |
| 17 Aug 2026, 10:28 | 1,273 | +3 |
| 13 Aug 2026, 17:57 | 1,270 | +2 |
| 10 Aug 2026, 20:41 | 1,268 | +3 |
| 8 Aug 2026, 03:59 | 1,265 | -1 |
| 7 Aug 2026, 08:32 | 1,266 | no change |
| 7 Aug 2026, 08:22 | 1,266 | first reading |
20 posts held, back to 7 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (7 August 2026 – 7 August 2026) |
| Views total | 100 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 08:32 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
A vulnerability labeled as critical has been found in nltk up to 3.9.4. The affected element is the function nltk.downloader of the component Downloader. Such manipulation leads to code injection.This vulnerability is uniquely identified as CVE-2026-12261. The attack can be launched remotely. No exploit exists. via VulDB Recent Entries https://ift.tt/pAKXlWT
A vulnerability identified as problematic has been detected in Estatik Real Estate Plugin up to 4.3.2 on WordPress. Impacted is an unknown function of the component OAuth Social Login Flow. This manipulation causes cross-site request forgery.This vulnerability is handled as CVE-2026-16262. The attack can be initiated remotely. There is not any exploit available.You should upgrade the affected component. via VulDB Re…
A vulnerability categorized as problematic has been discovered in Comments Plugin up to 7.6.59 on WordPress. This issue affects some unknown processing. The manipulation results in cross site scripting.This vulnerability is known as CVE-2026-15032. It is possible to launch the attack remotely. No exploit is available.It is advisable to upgrade the affected component. via VulDB Recent Entries https://ift.tt/sUghDtE
A vulnerability was found in Subscribe2 Plugin up to 10.45 on WordPress. It has been rated as problematic. This vulnerability affects unknown code. The manipulation leads to cross site scripting.This vulnerability is traded as CVE-2026-14331. It is possible to initiate the attack remotely. There is no exploit available.Upgrading the affected component is advised. via VulDB Recent Entries https://ift.tt/hn8QYU5
A vulnerability was found in MStore API Plugin up to 4.20.x on WordPress. It has been declared as problematic. This affects an unknown part. Executing a manipulation can lead to missing authorization.This vulnerability appears as CVE-2026-16038. The attack may be performed from remote. There is no available exploit.It is recommended to upgrade the affected component. via VulDB Recent Entries https://ift.tt/y4SBz8r
A vulnerability was found in MStore API Plugin up to 4.20.x on WordPress. It has been classified as critical. Affected by this issue is some unknown functionality. Performing a manipulation results in improper authentication.This vulnerability is reported as CVE-2026-16030. The attack is possible to be carried out remotely. No exploit exists.Upgrading the affected component is recommended. via VulDB Recent Entries h…
A vulnerability was found in Meow Gallery Plugin up to 5.5.1 on WordPress and classified as problematic. Affected by this vulnerability is an unknown functionality. Such manipulation leads to cross site scripting.This vulnerability is documented as CVE-2026-15386. The attack can be executed remotely. There is not any exploit available.It is suggested to upgrade the affected component. via VulDB Recent Entries https:…
A vulnerability has been found in Content Views Plugin up to 4.4 on WordPress and classified as critical. Affected is an unknown function. This manipulation causes sql injection.This vulnerability is registered as CVE-2026-15361. Remote exploitation of the attack is possible. No exploit is available.The affected component should be upgraded. via VulDB Recent Entries https://ift.tt/8eRUiyo
A vulnerability, which was classified as problematic, was found in BNE Testimonials Plugin on WordPress. This impacts an unknown function of the component Shortcode. The manipulation results in cross site scripting.This vulnerability is cataloged as CVE-2026-15245. The attack may be launched remotely. There is no exploit available.You should upgrade the affected component. via VulDB Recent Entries https://ift.tt/cTA…
A vulnerability classified as problematic was found in Events Manager Plugin up to 2.2.4 on WordPress. The impacted element is an unknown function. Executing a manipulation can lead to improper authentication.This vulnerability is tracked as CVE-2026-14205. The attack can be launched remotely. No exploit exists.Upgrading the affected component is advised. via VulDB Recent Entries https://ift.tt/o7MTVQZ
A vulnerability, which was classified as problematic, has been found in Password Protected Plugin up to 2.8.3 on WordPress. This affects an unknown function of the component REST API. The manipulation leads to information disclosure.This vulnerability is listed as CVE-2026-14943. The attack may be initiated remotely. There is no available exploit.It is advisable to upgrade the affected component. via VulDB Recent En…
A vulnerability classified as problematic has been found in MStore API Plugin up to 4.20.x on WordPress. The affected element is an unknown function. Performing a manipulation results in missing authorization.This vulnerability is identified as CVE-2026-16041. The attack can be initiated remotely. There is not any exploit available.It is recommended to upgrade the affected component. via VulDB Recent Entries https:/…
Showing the 12 most recent of 20 posts we hold for @cve_mitre_org. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 1 September 2026 — this entry's latest reading, not the date you are reading this.
“cve.mitre.org” (@cve_mitre_org), 1,301 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/cve_mitre_org.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.