CVE-2010-0713 json
Multiple cross-site request forgery (CSRF) vulnerabilities in Zenoss 2.3.3, and other versions before 2.5, allow remote attackers to hijack…
published 16y ago modified 4mo ago also EUVD-2010-0740
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 80%
- public exploits
- 1
- Exploit-DB
Summary
Multiple cross-site request forgery (CSRF) vulnerabilities in Zenoss 2.3.3, and other versions before 2.5, allow remote attackers to hijack the authentication of an administrator for (1) requests that reset user passwords via zport/dmd/ZenUsers/admin, and (2) requests that change user commands, which allows for remote execution of system commands via zport/dmd/userCommands/.
Is CVE-2010-0713 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-33536)
- Published
Exploit prediction
1.95% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-33536 Zenoss 2.3.3 - Multiple Cross-Site Request Forgery Vulnerabilities remote, 2010-01-18
- securityfocus.com http://www.securityfocus.com/bid/37843 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
-
securityfocus.com
/bid/37843
vdb-entry, exploit
-
zenoss.com
/news/SQL-Injection-and-Cross-Site-Forgery-in-Zenoss-Core-Corrected.html
vendor-advisory
-
secunia.com
/advisories/38195
third-party-advisory, vendor-advisory
- ngenuity.org /wordpress/2010/01/14/ngenuity-2010-002-zenoss-multiple-admin-csrf/
-
osvdb.org
/61805
vdb-entry
-
securityfocus.com
/archive/1/508982/100/0/threaded
mailing-list
Sources
- CVE List CVE-2010-0713
- NVD CVE-2010-0713
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.