Skip to content
Laskyr

Plugins · seo-local-rank · data as of 2026-11-04

Is TrueRanker safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.0.5)

As of 2026-11-04. 2 issues are on record for older versions; version 2.3.0 or newer fixes all of them that state a fix.

Latest version
3.0.5
Last updated
2026-10-22
Active installs
300+
Known issues on record
2
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 8.0+

AI Visibility Tracker and brand radar for ChatGPT, Gemini, Claude and more — plus Google rankings and backlinks from WordPress. — by TrueRanker Team

What to do

  1. Update to the latest version (3.0.5). Anything older than 2.3.0 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get seo-local-rank --field=version shows what you run; wp plugin update seo-local-rank updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.3 CVE-2026-1085 · published 2026-03-07

Cross-site request forgery (CSRF) in TrueRanker (2.2.9 and older)

Affected
2.2.9 and older
Fixed in
2.3.0 *
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The True Ranker plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.9. This is due to missing nonce validation on the seolocalrank-signout action. This makes it possible for unauthenticated attackers to disconnect the administrator's True Ranker account via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

NVD CVE-2026-1085Wordfence advisoryPlugin source

high 7.5 CVE-2021-39312 · published 2021-12-14

Path traversal / file read in TrueRanker (2.2.2 to 2.2.2)

Affected
2.2.2 to 2.2.2
Fixed in
2.2.4 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The True Ranker plugin <= 2.2.2 for WordPress allows arbitrary files, including sensitive configuration files such as wp-config.php, to be accessed via the src parameter found in the ~/admin/vendor/datatables/examples/resources/examples.php file.

NVD CVE-2021-39312packetstormsecurity.comWordfence advisoryPlugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
TrueRanker vulnerability status badge
<a href="https://laskyr.com/plugins/seo-local-rank"><img src="https://laskyr.com/plugins/seo-local-rank/badge.svg" alt="TrueRanker vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit