CVE-2012-4267 json
Cross-site scripting (XSS) vulnerability in user/register in Sockso 1.5 and earlier allows remote attackers to inject arbitrary web script…
published 2012-08-13 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-4211
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site scripting (XSS) vulnerability in user/register in Sockso 1.5 and earlier allows remote attackers to inject arbitrary web script or HTML via the name parameter.
Patch / fix
- github.com/rodnaph/sockso@fe2d895 commit
- github.com/rodnaph/sockso#99 pull request
Timeline
- First public exploit (EDB-18868)
- Published
Exploit prediction
3.56% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-18868 Sockso 1.51 - Persistent Cross-Site Scripting webapps, 2012-05-12
- github.com https://github.com/rodnaph/sockso/commit/fe2d895ea8eb8b8ccad5a3319f472e45d6ba5136 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/rodnaph/sockso/pull/99/files referenced PoC, tagged "exploit" by a source, unverified
- smwyg.com http://smwyg.com/blog/#sockso-persistant-xss-attack 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
/rodnaph/sockso/commit/fe2d895ea8eb8b8ccad5a3319f472e45d6ba5136
exploit, patch
-
github.com
/rodnaph/sockso/pull/99/files
exploit, patch
-
exploit-db.com
/exploits/18868
exploit
-
smwyg.com
/blog/#sockso-persistant-xss-attack
exploit, url-repurposed
-
secunia.com
/advisories/49148
third-party-advisory, vendor-advisory
- github.com /rodnaph/sockso/issues/93
Sources
- CVE List CVE-2012-4267
- NVD CVE-2012-4267
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.