Autopay · Security record
Is Autopay safe?
No known vulnerability affects the current version (5.1.0). 4 issues were found in earlier versions and fixed, the latest disclosed on Aug 18, 2026.
Checked 6 days ago against the WPVulnerability database, for version 5.1.0.
How it’s looked after
- Last release
- Oct 26, 2026 (2 weeks ago)
- Releases in the last year
- 16
- Tested up to
- WordPress 7.1.4
- Active installs
- 3K+
4 known vulnerabilities
- 2 high
- 2 not rated
None affects the current version.
Every known vulnerability in Autopay
Newest first, with any that affect the current version at the top.
Fixed in 5.0.1 · CVE-2026-90923 · Aug 18, 2026 · Wordfence
Fixed in 5.0.1 · CVE-2026-73338 · Aug 15, 2026 · Wordfence
Fixed in 5.0.1 · CVE-2026-15002 · Aug 15, 2026 · Wordfence
Fixed in 5.0.1 · CVE-2026-14293 · Aug 7, 2026 · Wordfence
Questions about Autopay’s security
Is Autopay safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Autopay updated: most attacks target sites that haven’t updated.
Does Autopay have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 4 older issues, fixed in earlier versions, so keep Autopay up to date.
Is Autopay still maintained?
Yes. Its last release was 2 weeks ago. No support threads were opened in the last two months.
Is Autopay 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.