WordPress security changelog
MEDIUM CVE-2014-2559 Modified

Twitget: Cross-site request forgery

Twitget is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

CVE / CNA score 6.8 CVSS · cve@mitre.org
NVD score 6.8 CVSS 2.0 · nvd@nist.gov
Component
Twitget
Plugin slug
twitget
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Oct 17, 2014
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Oct 17, 2014 and is one of 2 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Twitget to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical 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.

NVD vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Primary and upstream sources