WordPress plugin
oAuth Twitter Feed for Developers 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 oAuth Twitter Feed for Developers vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.4 | Authenticated (Administrator+) Stored Cross-Site Scripting ≤2.3.0No patch available | CVE-2023-25042 |
- Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting
≤2.3.0No patch available
oAuth Twitter Feed for Developers: common questions
Does oAuth Twitter Feed for Developers have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in oAuth Twitter Feed for Developers: 1 medium. At least one is not fixed in the latest version.
How do I check which version of oAuth Twitter Feed for Developers 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 oAuth Twitter Feed for Developers vulnerability?
CVE-2023-25042, published Jul 7, 2023: oAuth Twitter Feed for Developers <= 2.3.0 - Authenticated (Administrator+) Stored Cross-Site Scripting. Severity: Medium (CVSS 4.4).
Is any oAuth Twitter Feed for Developers vulnerability listed in CISA KEV?
No. None of the known oAuth Twitter Feed for Developers vulnerabilities is currently listed in the CISA KEV catalog.
