CVE-2009-4365 json
Multiple cross-site request forgery (CSRF) vulnerabilities in admin.php in ScriptsEz Ez Blog 1.0 allow remote attackers to hijack the authe…
published 16y ago modified 4mo ago also EUVD-2009-4333
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 2
- Exploit-DB
Summary
Multiple cross-site request forgery (CSRF) vulnerabilities in admin.php in ScriptsEz Ez Blog 1.0 allow remote attackers to hijack the authentication of administrators for requests that (1) add a blog via the add_blog action, (2) approve a comment via the approve_comment action, (3) change administrator information including the password via the admin_opt action, and (4) delete a blog via the delete action.
Is CVE-2009-4365 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-10461)
- Published
Exploit prediction
0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-10461 Ez Cart 1.0 - Multiple Cross-Site Request Forgery Vulnerabilities webapps, 2009-12-15
- EDB-10458 Ez Blog 1.0 - Cross-Site Scripting / Cross-Site Request Forgery webapps, 2009-12-15
- packetstormsecurity.org http://packetstormsecurity.org/0912-exploits/ezblog-xssxsrf.txt 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-352 Cross-Site Request Forgery
References
-
packetstormsecurity.org
/0912-exploits/ezblog-xssxsrf.txt
exploit
-
secunia.com
/advisories/37743
third-party-advisory, vendor-advisory
-
osvdb.org
/61114
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54895
vdb-entry
Sources
- CVE List CVE-2009-4365
- NVD CVE-2009-4365
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.