CVE-2012-5321 json
tiki-featured_link.php in TikiWiki CMS/Groupware 8.3 allows remote attackers to load arbitrary web site pages into frames and conduct phish…
published 2012-10-08 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5244
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.8%
- EPSS 13.8% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
tiki-featured_link.php in TikiWiki CMS/Groupware 8.3 allows remote attackers to load arbitrary web site pages into frames and conduct phishing attacks via the url parameter, aka "frame injection."
Timeline
- First public exploit (EDB-36848)
- Published
Exploit prediction
13.75% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-36848 Tiki Wiki CMS Groupware - 'url' Open Redirection webapps, 2012-02-18
- Nuclei template TikiWiki CMS Groupware v8.3 - Open Redirect nuclei detection template
- securitytracker.com http://www.securitytracker.com/id?1026708 referenced PoC, tagged "exploit" by a source, unverified
- st2tea.blogspot.com http://st2tea.blogspot.com/2012/02/tiki-wiki-cms-groupware-frame-injection.html referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/52079 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
securitytracker.com
/id?1026708
vdb-entry, exploit
-
st2tea.blogspot.com
/2012/02/tiki-wiki-cms-groupware-frame-injection.html
exploit
-
securityfocus.com
/bid/52079
vdb-entry, exploit
-
secunia.com
/advisories/48102
third-party-advisory, vendor-advisory
-
osvdb.org
/79409
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/73403
vdb-entry
Sources
- CVE List CVE-2012-5321
- NVD CVE-2012-5321
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.