CVE-2023-29218 json
The Twitter Recommendation Algorithm through ec83d01 allows attackers to cause a denial of service (reduction of reputation score) by arran…
published 2023-04-03 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-32796
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
The Twitter Recommendation Algorithm through ec83d01 allows attackers to cause a denial of service (reduction of reputation score) by arranging for multiple Twitter accounts to coordinate negative signals regarding a target account, such as unfollowing, muting, blocking, and reporting, as exploited in the wild in March and April 2023. NOTE: Vendor states that allowing users to unfollow, mute, block, and report tweets and accounts and the impact of these negative engagements on Twitter’s ranking algorithm is a conscious design decision, rather than a security vulnerability.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
References
-
github.com
/twitter/the-algorithm/issues/1386
issue-tracking, third-party-advisory
-
twitter.com
/elonmusk/status/1642324821324230657
third-party-advisory
-
steventey.com
/blog/twitter-algorithm
product
-
twitter.com
/aakashg0/status/1641976913165180929
third-party-advisory
-
twitter.com
/Kaptain_Kobold/status/1642379706925477888
third-party-advisory
-
github.com
/twitter/the-algorithm/tree/ec83d01dcaebf369444d75ed04b3625a0a645eb9
product
Sources
- CVE List CVE-2023-29218
- NVD CVE-2023-29218
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.