CVE-2013-0234 json
Cross-site scripting (XSS) vulnerability in the Twitter widget in Elgg before 1.7.17 and 1.8.x before 1.8.13 allows remote attackers to inj…
published 12y ago modified 4mo ago also EUVD-2013-0267
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in the Twitter widget in Elgg before 1.7.17 and 1.8.x before 1.8.13 allows remote attackers to inject arbitrary web script or HTML via the params[twitter_username] parameter to action/widgets/save.
Patch / fix
- github.com/Elgg/Elgg@a74a885 commit
- github.com/Elgg/Elgg@19dc507 commit
Is CVE-2013-0234 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 FencerExploit prediction
1.46% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/Elgg/Elgg/commit/19dc507c2fccb378be2a44a762edf6c1e7afa334#L0R11 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| 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 /Elgg/Elgg/commit/a74a88501c41e89c8bcd7fc650ae2f8cc0a5003d#L2L21
-
github.com
/Elgg/Elgg/commit/19dc507c2fccb378be2a44a762edf6c1e7afa334#L0R11
exploit, patch
-
secunia.com
/advisories/52007
third-party-advisory, vendor-advisory
- blog.elgg.org /pg/blog/cash/read/223/elgg-1813-and-1717
- packetstormsecurity.com /files/119903/Elgg-Twitter-Widget-Cross-Site-Scripting.html
-
seclists.org
/fulldisclosure/2013/Jan/251
mailing-list
-
openwall.com
/lists/oss-security/2013/01/29/4
mailing-list
-
securityfocus.com
/bid/57569
vdb-entry
Sources
- CVE List CVE-2013-0234
- NVD CVE-2013-0234
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.