CVE-2018-14888 json
inc/plugins/thankyoulike.php in the Eldenroot Thank You/Like plugin before 3.1.0 for MyBB allows XSS via a post or thread subject.
published 8y ago modified 4mo ago also EUVD-2018-6770
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.7%
- EPSS 3.7% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
inc/plugins/thankyoulike.php in the Eldenroot Thank You/Like plugin before 3.1.0 for MyBB allows XSS via a post or thread subject.
Patch / fix
- thank_you/like_project thank_you/like 3.1.0
- github.com/mybbgroup/MyBB_Thank-you-like-plugin#199 pull request
Is CVE-2018-14888 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-45178)
- Published
Exploit prediction
3.68% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-45178 MyBB Thank You/Like Plugin 3.0.0 - Cross-Site Scripting webapps, 2018-08-10
- packetstormsecurity.com http://packetstormsecurity.com/files/148871/MyBB-Thank-You-Like-3.0.0-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/mybbgroup/MyBB_Thank-you-like-plugin/pull/199
patch, third-party-advisory
-
exploit-db.com
/exploits/45178/
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/148871/MyBB-Thank-You-Like-3.0.0-Cross-Site-Scripting.html
exploit, third-party-advisory, vdb-entry
-
community.mybb.com
/mods.php?action=changelog&pid=360
vendor-advisory
Sources
- CVE List CVE-2018-14888
- NVD CVE-2018-14888
Fencer Intel 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.