CVE-2014-2023 json
Multiple SQL injection vulnerabilities in the Tapatalk plugin 4.9.0 and earlier and 5.x through 5.2.1 for vBulletin allow remote attackers…
published 9y ago modified 4mo ago also EUVD-2014-2075
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.1%
- EPSS 4.1% chance of exploitation in 30 days, percentile 90%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in the Tapatalk plugin 4.9.0 and earlier and 5.x through 5.2.1 for vBulletin allow remote attackers to execute arbitrary SQL commands via a crafted xmlrpc API request to (1) unsubscribe_forum.php or (2) unsubscribe_topic.php in mobiquo/functions/.
Is CVE-2014-2023 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-35102)
- Published
Exploit prediction
4.15% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-35102 Tapatalk for vBulletin 4.x - Blind SQL Injection webapps, 2014-10-28
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
exploit-db.com
/exploits/35102
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/70418
vdb-entry, third-party-advisory
-
packetstormsecurity.com
/files/128854/vBulletin-4.x-Tapatalk-Blind-SQL-Injection.html
third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2014/Oct/57
mailing-list, third-party-advisory
-
github.com
/tintinweb/pub/tree/master/pocs/cve-2014-2023
third-party-advisory
Sources
- CVE List CVE-2014-2023
- NVD CVE-2014-2023
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.