CVE-2014-9393: Multiple cross-site request forgery (CSRF) vulnerabilities in the Post to Twitter plugin 0.7 and earlier for W

Q: How do I fix CVE-2014-9393?

post to twitter: upgrade to newer than 0.7. Exact commands for each OS are on this page.

Q: Is CVE-2014-9393 being exploited?

CVE-2014-9393 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2014-9393 affect?

CVE-2014-9393 affects post to twitter. Severity is medium (CVSS 6.8). Multiple cross-site request forgery (CSRF) vulnerabilities in the Post to Twitter plugin 0.7 and earlier for WordPress allow remote attackers to hijack the authentication of administrators for requests that conduct cross-site scripting (XSS

Q: How urgent is CVE-2014-9393?

Priority 45/100. Public exploit reference

This month

MEDIUM 6.8UPGRADE

CVE-2014-9393 is a medium-severity flaw (CVSS 6.8) affecting post to twitter. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Multiple cross-site request forgery (CSRF) vulnerabilities in the Post to Twitter plugin 0.7 and earlier for WordPress allow remote attackers to hijack the authentication of administrators for requests that conduct cross-site scripting (XSS) attacks via the (1) idptt_twitter_username or (2) idptt_tweet_prefix parameter to wp-admin/options-general.php.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.8 (Medium)
EPSS exploit chance	1.0% (top 37%)
CISA exploited list	No
Weakness	CWE-352
Published	2014-12-31
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: post to twitter project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2014-12-31 21:59 UTCPublished CVE record published
2026-06-17 00:18 UTCUpdated Record last modified

post to twitter project post to twitter UPGRADE

Affected: <= 0.7

Fixed in: newer than 0.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy post-to-twitter || rpm -q post-to-twitter || post-to-twitter --version

2. UPGRADE to newer than 0.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade post-to-twitter

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade post-to-twitter

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2014-9393?

post to twitter: upgrade to newer than 0.7. Exact commands for each OS are on this page.

Is CVE-2014-9393 being exploited?

CVE-2014-9393 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2014-9393 affect?

CVE-2014-9393 affects post to twitter. Severity is medium (CVSS 6.8). Multiple cross-site request forgery (CSRF) vulnerabilities in the Post to Twitter plugin 0.7 and earlier for WordPress allow remote attackers to hijack the authentication of administrators for requests that conduct cross-site scripting (XSS

How urgent is CVE-2014-9393?

Priority 45/100. Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs