CVE-2015-1054 json
Cross-site scripting (XSS) vulnerability in the Games feature in Crea8Social 2.0 allows remote authenticated users to inject arbitrary web…
published 11y ago modified 4mo ago also EUVD-2015-1197
- cvss
- 3.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site scripting (XSS) vulnerability in the Games feature in Crea8Social 2.0 allows remote authenticated users to inject arbitrary web script or HTML via the Game Content field in Add Game.
Is CVE-2015-1054 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-35691)
- Published
Exploit prediction
2.93% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-35691 Crea8Social 2.0 - Cross-Site Scripting Change Interface webapps, 2015-01-04
- packetstormsecurity.com http://packetstormsecurity.com/files/129816/Crea8Social-2.0-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
exploit-db.com
/exploits/35691
exploit
-
packetstormsecurity.com
/files/129816/Crea8Social-2.0-Cross-Site-Scripting.html
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/99615
vdb-entry
- codecanyon.net /item/crea8social-php-social-networking-platform-v31/9211270/support
- codecanyon.net /item/crea8social-php-social-networking-platform-v31/9211270
-
osvdb.org
/show/osvdb/116732
vdb-entry
Sources
- CVE List CVE-2015-1054
- NVD CVE-2015-1054
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.