Advanced 301 and 302 Redirect · Security record
Is Advanced 301 and 302 Redirect safe?
No known vulnerability affects the current version (1.8.2). 1 issue was found in earlier versions and fixed, the latest disclosed on Jun 8, 2026.
Checked 3 days ago against the WPVulnerability database, for version 1.8.2.
How it’s looked after
- Last release
- Aug 14, 2026 (2 months ago)
- Releases in the last year
- 43
- Tested up to
- WordPress 7.1.4
- Active installs
- 1K+
1 known vulnerability
- 1 critical
None affects the current version.
Every known vulnerability in Advanced 301 and 302 Redirect
Newest first, with any that affect the current version at the top.
- critical
Unauthenticated SQL Injection
Fixed in 1.7.0 · CVE-2026-49067 · Jun 8, 2026 · Wordfence
Questions about Advanced 301 and 302 Redirect’s security
Is Advanced 301 and 302 Redirect safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Advanced 301 and 302 Redirect updated: most attacks target sites that haven’t updated.
Does Advanced 301 and 302 Redirect have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Advanced 301 and 302 Redirect up to date.
Is Advanced 301 and 302 Redirect still maintained?
Yes. Its last release was 2 months ago. No support threads were opened in the last two months.
Is Advanced 301 and 302 Redirect 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.