Quick Page/Post Redirect backdoor: how to check and clean a site
Quick Page/Post Redirect, a redirect plugin with more than 70,000 installations, shipped a hidden update channel in versions 5.2.1 and 5.2.2. In March 2021 that channel delivered a tampered 5.2.3, which injected spam into posts for logged-out visitors and could receive arbitrary code. The tampered build carries the same version number as the clean one. WordPress.org closed the plugin on 14 April 2026, and Patchstack assigned CVE-2026-126697 on 14 November, so scanners now flag every site that still has the plugin. The clean 5.2.4 cannot be downloaded, so for nearly every site the fix is to export the redirects and remove the plugin.
Prepared by G. Schad, WordPress and Linux security specialist
Quick Page/Post Redirect: the 2021 backdoor now has a CVE, so scanners will start flagging it
Patchstack published CVE-2026-126697 on 14 November for a backdoor in Quick Page/Post Redirect, versions 5.2.1 to 5.2.3. It rates the flaw 10, needing no login, and notes that no mitigation rule can be written for it. The backdoor itself is not new. Austin Ginder of the hosting company Anchor found it in April, after twelve sites in his fleet raised alerts. WordPress.org closed the plugin on 14 April for a security issue, and BleepingComputer reported the findings on 29 April. What is new is the identifier: vulnerability scanners and host dashboards will now flag every site that still has the plugin installed. It had more than 70,000 installations when it was closed.
How it worked, according to Ginder’s findings as reported. Versions 5.2.1 and 5.2.2, from 2020 and 2021, contained a hidden self-update mechanism that checked a server at anadnet.com instead of WordPress.org. WordPress.org had that code removed from later versions in February 2021. In March 2021, though, sites still on 5.2.1 or 5.2.2 received a tampered 5.2.3 from the external server, with a different hash from the 5.2.3 on WordPress.org. The tampered build hooks the_content and, for visitors who are not logged in, fetches content from the anadnet server and inserts it into posts. That is cloaked SEO spam the site owner never sees. It also keeps the private updater, which can push arbitrary code to the site on demand. At the time of the April report, the subdomain that served the tampered build did not resolve, so the channel was dormant, but the domain itself was live.
Two details make this harder than an ordinary vulnerable plugin. First, the tampered build reports the same version number as the clean 5.2.3, so a version check cannot tell them apart. Second, the fix Patchstack lists, 5.2.4, cannot be downloaded. The WordPress.org listing still shows 5.2.4 as the last version, last updated in 2023, but the plugin has been closed since 14 April and isn’t available. For most sites, the fix is to remove the plugin and move the redirects somewhere else.
Figure 1 · At a glance
Same version number, different code: remove the plugin, keep the redirects.
Question
Answer
Affected
Quick Page/Post Redirect 5.2.1 to 5.2.3; tampered 5.2.3 delivered in March 2021
What it did
Spam injected for logged-out visitors; an updater able to push code
Status
Closed on WordPress.org since 14 April 2026; CVE published 14 November
Fix
Export the redirects, then delete the plugin; 5.2.4 cannot be downloaded
Look for
An updater/ folder, or a main file unlike WordPress.org’s copy of that version
The points that decide what to do about the Quick Page/Post Redirect backdoor CVE-2026-126697, as stated in the sections below.
Find it, save the redirects, remove it, and check what it served
Do this for every site on the server, including staging copies. The redirects are usually the only reason the plugin is still installed, so export them before you delete anything.
01
Find every installation
By plugin list and by folder, across all accounts:
shell
$ for s in /home/*/public_html;dowp plugin list --path="$s"--skip-plugins--skip-themes--fields=name,status,version--format=csv2>/dev/null|grep-i"quick-pagepost-redirect"|sed"s|^|$s |";done$ find /home/*/public_html -maxdepth 4 -type d -name"quick-pagepost-redirect-plugin"2>/dev/null
An inactive copy still counts: its files are on disk, and they can be requested directly.
02
Look for the update channel
Searching for the author’s name does not work: the clean releases mention anadnet.com in a dozen places, including a FAQ feed they fetch. Look instead for the update channel itself, an updater folder or an update checker pointed at anadnet.com/updates. In WordPress.org’s repository today, the 5.2.1 tag carries both and the 5.2.2 to 5.2.4 tags carry neither:
A match means the site had a channel that could deliver code from outside WordPress.org. Treat the site as possibly compromised and review all of it, not just the plugin.
03
Compare the main file with WordPress.org’s copy
The repository still serves each released version, even with the plugin closed. Run this in each plugin folder; it reads the version the file claims and compares the file with that tag:
A difference on a site that reports 5.2.3 is the tampered build, which carries the same version number as the clean one. Treat that site as compromised.
04
Export the redirects
The plugin’s source keeps its Quick Redirects in the quickppr_redirects option and each post’s redirect in post meta under _pprredirect_url, with _pprredirect_type for the status code. Export both before removing it:
WP-CLI
$ wp option get quickppr_redirects --format=json--skip-plugins--skip-themes> quickppr_redirects.json$ wp db query "SELECT post_id, meta_value FROM $(wp db prefix --skip-plugins --skip-themes)postmeta WHERE meta_key = '_pprredirect_url'"--skip-plugins--skip-themes> ppr_post_redirects.tsv
Recreate the redirects you need as server rules (Redirect 301 in .htaccess, or return 301 in nginx) or in a maintained redirect plugin, and test them before the next step.
You can only reinstall 5.2.4 from a copy you already hold and have verified; the WordPress.org download is closed.
06
If the tampered build was there, treat the site as compromised
Review administrators, must-use plugins, PHP files in uploads and scheduled events. Rotate the salts and the administrator passwords. Check Search Console for pages or links you did not publish: the spam was only shown to logged-out visitors and crawlers.
WP-CLI
$ wp user list --role=administrator--fields=ID,user_login,user_registered--skip-plugins--skip-themes$ wp config shuffle-salts --skip-plugins--skip-themes
While you work, block outbound connections to anadnet.com at the firewall, so a revived update channel cannot deliver anything new.
Common questions about the Quick Page/Post Redirect backdoor
A scanner flags Quick Page/Post Redirect with CVE-2026-126697. Is my site hacked?
Not necessarily. The CVE covers 5.2.1 to 5.2.3 because of the hidden update channel and the tampered 5.2.3 it delivered; the copies of 5.2.2 and 5.2.3 on WordPress.org do not contain the channel. The two checks on this page answer it: an updater folder or update checker, and a main file that differs from WordPress.org’s copy of the same version. Neither: remove the plugin and move on. Either: treat the site as compromised. The plugin has to go in both cases, because no clean update can be downloaded.
Can I just update Quick Page/Post Redirect to 5.2.4?
Not from WordPress.org: the plugin was closed on 14 April 2026 and cannot be downloaded. Export the redirects, recreate them in the server configuration or in a maintained plugin, and delete it.
Choose the response path
The redirect plugin was there for years: choose the response path.
The servers under the sites
Get Apache, HTTP/2 and the rest of the web stack checked on every host.
Best when several servers need the Apache version, the protocols per virtual host and the backported packages verified from the running process, the look-back since 11 November done once, and a written result per host.
Get the finding classified and the site restored to a trusted state.
Best when a file-upload plugin left PHP in uploads, wp-config.php went missing, the tampered Quick Page/Post Redirect build turned up, or an account changed hands, and you want every layer removed in one pass.