WordPress plugin
Send to Twitter security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All Send to Twitter vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Cross-Site Request Forgery to Stored Cross-Site Scripting ≤1.7.2No patch available | CVE-2025-23691 |
- Medium6.1Cross-Site Request Forgery to Stored Cross-Site Scripting
≤1.7.2No patch available
Send to Twitter: common questions
Does Send to Twitter have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Send to Twitter: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Send to Twitter I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Send to Twitter vulnerability?
CVE-2025-23691, published Jan 16, 2025: Send to Twitter <= 1.7.2 - Cross-Site Request Forgery to Stored Cross-Site Scripting. Severity: Medium (CVSS 6.1).
Is any Send to Twitter vulnerability listed in CISA KEV?
No. None of the known Send to Twitter vulnerabilities is currently listed in the CISA KEV catalog.