CVE-2014-2559
Summary
| CVE | CVE-2014-2559 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2014-10-17 22:55:04 UTC |
| Updated | 2026-05-06 22:30:45 UTC |
| Description | Multiple cross-site request forgery (CSRF) vulnerabilities in twitget.php in the Twitget plugin before 3.3.3 for WordPress allow remote attackers to hijack the authentication of administrators for requests that change unspecified plugin options via a request to wp-admin/options-general.php. |
Risk And Classification
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
MediumAuthentication
NoneConfidentiality
PartialIntegrity
PartialAvailability
PartialAV:N/AC:M/Au:N/C:P/I:P/A:P
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Twitget Project | Twitget | All | All | All | All |
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| CSRF/XSS vulnerability in Twitget 3.3.1 – dxw advisories | af854a3a-2127-422b-91ae-364da2661108 | security.dxw.com | Exploit |
| Security Advisory SA57892 - WordPress Twitget Plugin Cross-Site Request Forgery Vulnerability - Secunia | af854a3a-2127-422b-91ae-364da2661108 | secunia.com | |
| Twitget 3.3.1 Cross Site Request Forgery / Cross Site Scripting ≈ Packet Storm | af854a3a-2127-422b-91ae-364da2661108 | packetstormsecurity.com | Exploit |
| WordPress › Twitget « WordPress Plugins | af854a3a-2127-422b-91ae-364da2661108 | wordpress.org | Vendor Advisory |
| Full Disclosure: CSRF/XSS vulnerability in Twitget 3.3.1 (WordPress plugin) | af854a3a-2127-422b-91ae-364da2661108 | seclists.org | Exploit |
| IBM X-Force Exchange | af854a3a-2127-422b-91ae-364da2661108 | exchange.xforce.ibmcloud.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.