CVE-2010-2039 json
Cross-site request forgery (CSRF) vulnerability in gpEasy CMS 1.6.2, 1.6.1, and earlier allows remote attackers to hijack the authenticatio…
published 16y ago modified 4mo ago also EUVD-2010-2059
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site request forgery (CSRF) vulnerability in gpEasy CMS 1.6.2, 1.6.1, and earlier allows remote attackers to hijack the authentication of administrators for requests that create new administrative users via an Admin_Users action to index.php. NOTE: some of these details are obtained from third party information.
Is CVE-2010-2039 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-12441)
- Published
Exploit prediction
1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-12441 gpEasy 1.6.1 - Cross-Site Request Forgery (Add Admin) webapps, 2010-04-28
- packetstormsecurity.org http://packetstormsecurity.org/1004-exploits/gpeasy-xsrf.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
exploit-db.com
/exploits/12441
exploit
-
packetstormsecurity.org
/1004-exploits/gpeasy-xsrf.txt
exploit
-
vupen.com
/english/advisories/2010/1030
vdb-entry, vendor-advisory
-
secunia.com
/advisories/39643
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/58214
vdb-entry
-
osvdb.org
/64130
vdb-entry
Sources
- CVE List CVE-2010-2039
- NVD CVE-2010-2039
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.