CVE-2007-1244 json
Cross-site request forgery (CSRF) vulnerability in the AdminPanel in WordPress 2.1.1 and earlier allows remote attackers to perform privile…
published 2007-03-03 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-1241
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.5%
- EPSS 7.5% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site request forgery (CSRF) vulnerability in the AdminPanel in WordPress 2.1.1 and earlier allows remote attackers to perform privileged actions as administrators, as demonstrated using the delete action in wp-admin/post.php. NOTE: this issue can be leveraged to perform cross-site scripting (XSS) attacks and steal cookies via the post parameter.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 2.1.2-1
debian advisories DEBIAN-CVE-2007-1244
- securityfocus.com/bid/22735 advisory
Timeline
- First public exploit (EDB-29682)
- Published
Exploit prediction
7.54% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-29682 WordPress Core 2.1.1 - 'post.php' Cross-Site Scripting webapps, 2007-02-26
- securityfocus.com http://www.securityfocus.com/bid/22735 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
- Technology feeds
References
-
securityfocus.com
/bid/22735
vdb-entry, exploit, patch, vendor-advisory
-
gentoo.org
/security/en/glsa/glsa-200703-23.xml
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/32703
vdb-entry
-
archives.neohapsis.com
/archives/fulldisclosure/2007-02/0583.html
mailing-list
-
securityfocus.com
/archive/1/461351/100/0/threaded
mailing-list
-
secunia.com
/advisories/24566
third-party-advisory
-
osvdb.org
/33787
vdb-entry
-
osvdb.org
/33788
vdb-entry
Sources
- CVE List CVE-2007-1244
- NVD CVE-2007-1244
Fencer Vulns 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.