- Reproduce first: test as a new mobile visitor, not as yourself — redirect hacks are conditional
- Update or delete the vulnerable sharing/design plugins; in this wave, updating promptly was the whole game
- Clean injected code from posts, widgets, theme files and the database, then scan remotely
- Rotate credentials and audit admins; a redirect is a symptom, and the access behind it is the disease
This post is part of our series on WordPress attacks in the last 10 years — one major attack per day, what it was, how to detect it, how to remove it and how to keep it out. This instalment covers The 2019 Redirect Wave: Social Warfare, Yuzo and Yellow Pencil (2019).
What happened
Spring 2019 delivered a cluster, not a single bug: a stored cross-site scripting flaw in Social Warfare (a social-sharing plugin), flaws in Yuzo Related Posts, and a privilege-escalation flaw in the Yellow Pencil design plugin were all disclosed and exploited in the same season. Patchstack’s later reporting found the Social Warfare flaw still being actively exploited years afterwards — abandoned vulnerable versions never stop being useful to attackers. The payloads were commercial rather than theatrical: visitors were redirected to malvertising and scam pages while owners saw their sites working normally.
Who was exposed: Sites running vulnerable versions of the Social Warfare, Yuzo Related Posts or Yellow Pencil Visual Theme Customizer plugins. Why it mattered: The wave put redirect and malvertising injections onto large numbers of ordinary business sites — and years later, the Social Warfare flaw was still listed among the most-exploited old vulnerabilities.
How this attack works
Each flaw gave a different grade of access — script injection into pages visitors load, or settings changes that let attackers act above their role — but the monetisation converged: inject code once, redirect a slice of real human traffic to ad-fraud and scam destinations, stay quiet. Redirect hacks choose a percentage and conditions (new visitors, mobile users, specific countries) precisely so that the owner, a repeat desktop visitor, rarely triggers it.
The exploitation itself is usually automated end to end. Bots continuously scan the web reading plugin readme files and version strings; the moment a vulnerable version is fingerprinted, an exploit script fires — creating an admin account, uploading a web shell, or injecting a database payload, depending on the flaw. The site owner typically did nothing ‘wrong’ on the day it happened beyond running a popular plugin a few versions behind, which is why the median time from disclosure to mass attack — about five hours for the worst flaws in 2025 — matters so much.
Signs your site has it — and how to confirm
- Visitors — especially first-time or mobile visitors — report being redirected to strange ad or scam pages
- Your site behaves for you but not for customers; testing in an incognito window on mobile data reproduces it
- New script or iframe code in posts, widgets or theme files pointing at ad networks you never joined
- Traffic in analytics falls while bounce behaviour looks bizarre — people are being stolen mid-visit
Confirm the plugin and its version on your site against the affected versions in the advisory — if you are at or below the vulnerable version, treat the site as exposed, not just at risk. Then check for the fingerprints of a successful exploit: admin users you did not create, files modified after the disclosure date, PHP files in uploads, and unfamiliar options or cron jobs in the database.
Step-by-step removal and recovery
Immediate actions for this attack
- Reproduce first: test as a new mobile visitor, not as yourself — redirect hacks are conditional
- Update or delete the vulnerable sharing/design plugins; in this wave, updating promptly was the whole game
- Clean injected code from posts, widgets, theme files and the database, then scan remotely
- Rotate credentials and audit admins; a redirect is a symptom, and the access behind it is the disease
The full protocol
- Back up first, labelled infected — you may need it for evidence or rollback.
- Update the vulnerable plugin immediately if a fix exists; if none exists, deactivate and delete it — an unpatched known flaw is an open door.
- Assume entry may already have happened: audit every administrator account (including in the database, where hidden admins do not show in wp-admin).
- Scan files and database: recently modified PHP, PHP in uploads, encoded payloads in wp_options, rogue cron jobs.
- Reinstall the plugin (and ideally core and theme) from clean official sources rather than trusting edited files.
- Rotate wp-admin, hosting, database and FTP credentials, and regenerate wp-config.php salt keys to kill every existing session.
- Verify with a fresh fetch of key pages and a server-side scan, then watch file-change alerts closely for two weeks — reinfection almost always means a persistence point survived.
How to prevent it
- Sharing buttons and design customisers are real attack surface — audit them like any other plugin
- Delete plugins you no longer use; the most-exploited flaws are often in forgotten extensions
- Monitor your own site as a visitor: an occasional incognito + mobile check catches conditional redirects
- Keep a remote scanner watching; redirect payloads are built to evade owner-side detection
The defences repeat across this whole series for a reason: kept-updated software, unique passwords with 2FA, the fewest possible plugins, backups stored off the server, and monitoring that looks at your site the way an attacker — or Google — does. Sites rarely fall to one exotic trick; they fall to one ordinary gap.
FAQs
Why do redirects only happen sometimes?
Conditions are the camouflage. Redirect code typically fires for new visitors, mobile devices, or specific referrers, and only a percentage of the time — so reports sound unreliable and owners dismiss them.
Social Warfare was fixed years ago. Why is it in a 2026 guide?
Because attackers still scan for it. A flaw stops mattering when the last vulnerable site updates or deletes the plugin — and that tail lasts for years.
Is a redirect hack an SEO problem or a security problem?
Security first. The redirect is monetised access; until the access is closed and the injection cleaned, SEO fixes are repainting a house someone else holds keys to.
Next in the series and the full timeline: WordPress Attacks in the Last 10 Years — the complete guide.
JunoBizz audits, cleans and hardens WordPress sites — cloaked spam, rogue admins, poisoned plugins and everything in this series. Get the checks run before Google finds the problem.
Talk to JunoBizz