Rank Math SEO PRO 3.0.123 Compromised: Act Now

By Bug Circuit Security Team
Rank Math SEO PRO 3.0.123 Compromised: Act Now

Is your own website affected? Check it free in 2 minutes.

Passive outside check only. Nothing is attacked, no signup.

If you downloaded or updated Rank Math SEO PRO 3.0.123 between October 15, 2026 at 20:02 UTC and October 16, 2026 at 07:12 UTC, your copy may have been one of the affected packages, and if you activated it, Rank Math says to treat your site as compromised: update to version 3.0.124, then follow the cleanup steps below.

Who this is for and what you'll get

This post is for owners of WordPress sites that use the paid Rank Math SEO PRO plugin, and for the agencies and freelancers who look after those sites. You will learn what happened, how to tell whether you are in the affected group, and exactly what to check and change. No security background needed.

The facts below come from the National Vulnerability Database (NVD) entry for CVE-2026-111862 and from Rank Math's own incident page. Check Rank Math's page for its latest guidance, because it is the vendor's source of truth.

What happened, in plain English

This was not a normal bug that a hacker finds in your site. It was a supply-chain compromise. That means the plugin package itself, the thing you download and install, contained malicious code. The weakness is filed as CWE-506, Embedded Malicious Code.

Per the NVD record, a subset of Rank Math SEO PRO 3.0.123 packages downloaded or updated in that roughly 11-hour window carried malware. Rank Math says the malware could compromise a site if the plugin was activated. Rank Math removed the affected files and released version 3.0.124 as the clean replacement.

The record lists a CVSS score of 9.8 (Critical). CVSS is a standard 0 to 10 severity scale. The NVD status is currently "Deferred," which means NVD has not prioritized its own analysis of this entry, so the details come from the record as published, not from an NVD review.

What the malware may do

Rank Math states the malware may:

  • Set up persistent access, so the attacker can return even after you update.
  • Contact a server at rank1cdn[.]com. (The brackets keep the name from being a clickable link. Do not visit it.)
  • Recreate hidden backdoors whenever someone visits a page.
  • Expose WordPress credentials, database credentials, API keys and other secrets that the web server can read.

That last point matters most. If the malware ran, updating the plugin does not undo what was already copied or planted. This is why Rank Math tells sites that activated an affected package to treat the website as compromised.

Are you affected? A quick decision table

Version 3.0.123 alone does not prove you were hit. What matters is when your copy was downloaded or updated and whether it was activated.

Your situationWhat it meansWhat to do
Plugin downloaded or updated inside the window and activatedYour copy may be one of the affected packages (only a subset of 3.0.123 packages carried malware)Rank Math says to treat the site as compromised. Follow all steps below.
Inside the window, but never activatedRank Math says the risk was tied to activationDelete that copy, install 3.0.124, and still run the checks as a precaution.
Downloaded or updated before October 15, 20:02 UTC, or after October 16, 07:12 UTCOutside the vendor-confirmed windowUpdate to the latest version and check the changelog.
You are not sure when it was updatedYou cannot rule it outAssume you are in the window and run the checks.
You use only the free Rank Math SEO pluginThe record covers Rank Math SEO PRO onlyNo action from this record. Keep the plugin updated.

To find your install date, look at your hosting control panel's file manager (modified date of the plugin folder), your backup history, and your update or deploy logs. Dates on files can be changed, so treat them as a hint, not proof.

Step-by-step: what to do now

Work in this order. The order matters, and we explain why in step 5.

1. Take a snapshot first

Make a full backup of your files and database and store it somewhere offline. You may need it later to see what changed. Do not overwrite your only good backup.

2. Update to Rank Math SEO PRO 3.0.124 or later

In WordPress, go to Plugins > Installed Plugins, update Rank Math SEO PRO, and confirm the version number. Then read the Rank Math changelog for anything newer. If you have shell access, WP-CLI (the WordPress command line tool) can show the version. Replace /path/to/site with your WordPress folder. The --skip-plugins and --skip-themes flags stop WordPress from loading plugins and themes, so a possibly malicious plugin does not run while you check.

wp --path=/path/to/site --skip-plugins --skip-themes plugin list --fields=name,version,status | grep -i rank

If you were in the affected group, treat this update as stopping the source, not as the cleanup.

3. Hunt for signs of compromise

Rank Math lists these indicators: three malicious entries in the wp_options database table, hidden PHP backdoors, unauthorized administrator accounts, a fake WordPress core file, PHP-executable .cache files, and a system cron marker. Use Rank Math's page for the exact names, because we do not want to guess at them here.

Here are safe, read-only checks you can run over SSH. Replace /path/to/site with your WordPress folder. The wp commands use --path, so they work from any folder, and --skip-plugins --skip-themes keeps the suspect plugin from loading.

# List all administrator accounts. Look for names you do not recognize.
wp --path=/path/to/site --skip-plugins --skip-themes user list --role=administrator --fields=ID,user_login,user_email,user_registered

# Search all files for the domain named in the advisory.
grep -rIl "rank1cdn" /path/to/site

# Find .cache files, then see which of them contain PHP code.
find /path/to/site/wp-content -type f -name "*.cache"
grep -rl "<?php" --include="*.cache" /path/to/site/wp-content

# Compare WordPress core files against the official checksums.
wp --path=/path/to/site --skip-plugins --skip-themes core verify-checksums

Two notes. A .cache file with PHP code inside is a red flag, because normal cache files do not need to run as code. And wp core verify-checksums can flag unexpected files inside core folders, which may help spot a fake core file.

Also check scheduled jobs (cron). Rank Math lists a "system cron marker," and cron entries can live in several places, not only in one user's list. Run these read-only checks:

# Entries dropped into the system cron folder.
ls -la /etc/cron.d

# The main system crontab.
cat /etc/crontab

# The web server user's crontab (the name varies by host, often www-data).
sudo crontab -l -u www-data

Repeat the last command as sudo crontab -l -u <user> for every other user on the server, replacing <user> with that account name. Look for lines or files you did not create, and compare what you find with the cron marker described on Rank Math's incident page. If you only have a shared host with no shell, ask your host's support to run these checks, or use the file manager and the Users screen.

4. Clean up, or restore from a clean backup

The safest route is to restore a backup taken before October 15, 2026, then install 3.0.124 straight away. Because the malware may recreate backdoors, deleting the files you find one by one can leave something behind.

If you have no clean backup, you have two choices. Hire a professional to clean the site, or rebuild: fresh WordPress core, fresh plugins and themes from official sources, and your content exported carefully. Remove any administrator account you did not create.

5. Change every secret, after the site is clean

Do this after cleanup, not before. If a backdoor is still active, new passwords can be stolen right away.

  • All WordPress admin and editor passwords.
  • The database password. Change it for the database user, then update DB_PASSWORD in wp-config.php.
  • Hosting, SFTP and SSH passwords, and SSH keys.
  • API keys for payment, email, analytics and any other service the site talks to.
  • The WordPress security keys (salts). Generate fresh ones from WordPress.org's salt generator and paste them into wp-config.php. This logs everyone out, which is what you want.

Turn on two-factor authentication for admin accounts while you are at it.

6. Watch and decide who to tell

Keep an eye on your access logs, new admin accounts and outgoing email for the next few weeks. If your site stored customer data, think about whether it could have been exposed. Notification rules vary by country and industry, so ask a qualified adviser if you are unsure. Our website hacked guide walks through the wider recovery process.

What this does not tell us

  • We do not know how many sites were hit. The record does not give a number, so we will not guess.
  • The NVD record lists no affected-version range beyond the description. Do not assume every 3.0.123 install is bad, and do not assume a clean-looking site is safe if you were in the window.
  • A passive outside scan cannot see inside your files. Our free website security check looks at your domain from the outside (subdomains, technology, DNS and email security), so it is useful for exposure, but it will not tell you whether this plugin infected your server.

Why this kind of attack is hard to spot

Most WordPress advice says to update plugins quickly, and that is still good advice. This incident shows the other side: the update channel itself can be the problem. That is rare, but it is why backups, least-privilege accounts and a habit of reading vendor notices all matter. For a wider look at where your site may be exposed, see how to tell if your website is hackable.

Key takeaways

  • Only a subset of packages downloaded or updated between October 15, 2026 20:02 UTC and October 16, 2026 07:12 UTC carried malware. Version 3.0.123 alone does not prove compromise.
  • If you activated an affected package, treat the site as compromised and do not rely on the update alone.
  • Update to 3.0.124 or later, check the indicators on Rank Math's incident page (including cron entries in more than one place), and prefer restoring a backup from before October 15.
  • Rotate passwords, database credentials, API keys and WordPress salts only after the site is clean.
  • Keep offline backups and read vendor security notices, since a trusted update can also be the risk.

What a Bug Circuit audit can and cannot do

A Bug Circuit audit is a manual security test of your website by a real person, ending in a written report with every issue, its severity, evidence and fix steps. It is a small-site audit, not a forensic investigation, a compliance certificate or a full incident-response cleanup. It can show you what else is weak around your site, and later audits retest the previous report. Fixes are quoted separately per issue. You can see the details on the pricing page.

Want certainty, not guesswork?

A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.

See pricing

Frequently asked questions

Is Rank Math 3.0.123 compromised?
Only a subset of Rank Math SEO PRO 3.0.123 packages carried malware. Those affected are among the packages downloaded or updated between October 15, 2026 at 20:02 UTC and October 16, 2026 at 07:12 UTC. Version 3.0.123 by itself is not enough to say a site was hit, so check when your copy was obtained.
Is my WordPress site infected with Rank Math malware?
It might be if you activated an affected package from that time window. Check for administrator accounts you did not create, PHP code inside .cache files, references to rank1cdn, and the other indicators on Rank Math's incident page. If you find any, treat the site as compromised and follow the cleanup steps.
Rank Math supply chain attack: what should I do?
Update Rank Math SEO PRO to 3.0.124 or later and check the changelog for newer releases. If you were in the affected window, back up the site, look for the listed indicators, restore a clean backup from before October 15 if you can, then rotate all passwords, API keys and WordPress salts.
Will updating to Rank Math 3.0.124 remove the malware?
Not necessarily. The update replaces the plugin with a clean version, but the malware may have left hidden backdoors, new admin accounts or other changes. Rank Math tells sites that activated an affected package to treat the website as compromised.
Do I need to worry about the free Rank Math SEO plugin?
The NVD record for CVE-2026-111862 covers Rank Math SEO PRO only. It does not mention the free plugin. Keep the free plugin updated as usual and watch Rank Math's announcements.

Keep reading

See what attackers see, for free

Run the free passive check on your website. No login, no impact on your site, results in seconds.

Ready for the full manual audit? See pricing

Published by Bug Circuit. Written with AI assistance and reviewed for accuracy before publishing.