Autopost for X (formerly Autoshare for Twitter) · Security record
Is Autopost for X (formerly Autoshare for Twitter) safe?
No known vulnerability affects the current version (2.3.4). 4 issues were found in earlier versions and fixed, the latest disclosed on Jan 22, 2026.
Checked 5 days ago against the WPVulnerability database, for version 2.3.4.
How it’s looked after
- Last release
- Sep 2, 2026 (2 months ago)
- Releases in the last year
- 4
- Tested up to
- WordPress 7.1.4
- Active installs
- 5K+
4 known vulnerabilities
- 1 critical
- 2 high
- 1 medium
None affects the current version.
Disclosed each year
- 20223
- 20261
Every known vulnerability in Autopost for X (formerly Autoshare for Twitter)
Newest first, with any that affect the current version at the top.
- medium
Missing Authorization
Fixed in 2.3.2 · CVE-2026-25311 · Jan 22, 2026 · Wordfence
- critical
Remote Code Execution
Fixed in 1.3.0 · CVE-2022-25912 · Dec 5, 2022 · Wordfence
Fixed in 1.3.0 · CVE-2022-38900 · Nov 28, 2022 · Wordfence
Fixed in 1.2.0 · CVE-2022-25858 · Jul 15, 2022 · Wordfence
Questions about Autopost for X (formerly Autoshare for Twitter)’s security
Is Autopost for X (formerly Autoshare for Twitter) safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Autopost for X (formerly Autoshare for Twitter) updated: most attacks target sites that haven’t updated.
Does Autopost for X (formerly Autoshare for Twitter) have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 4 older issues, fixed in earlier versions, so keep Autopost for X (formerly Autoshare for Twitter) up to date.
Is Autopost for X (formerly Autoshare for Twitter) still maintained?
Yes. Its last release was 2 months ago. No support threads were opened in the last two months.
Is Autopost for X (formerly Autoshare for Twitter) compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.