Skip to content
Laskyr

Plugins · google-pagerank-display · data as of 2026-11-04

Is Google PageRank Display safe? Known vulnerabilities and latest version

Google PageRank Display is closed on wordpress.org

Closed on 2026-04-15 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you.

Status
Closed 2026-04-15
Known issues on record
1
Unpatched in latest
0

What to do

  1. Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
  2. Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
  3. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate google-pagerank-display && wp plugin delete google-pagerank-display

Check your version

Known vulnerabilities

1 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. 1 record(s) do not state which versions are affected.

medium 4.3 CVE-2026-6294 · published 2026-04-22

Cross-site request forgery (CSRF) in Google PageRank Display (1.4 and older)

Affected
1.4 and older
Fixed in
unknown
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 Google PageRank Display plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to and including 1.4. This is due to missing nonce validation in the gpdisplay_option() function, which handles the plugin settings page. The settings form does not include a wp_nonce_field(), and the form handler does not call check_admin_referer() or wp_verify_nonce() before processing the POST request. This makes it possible for unauthenticated attackers to trick a logged-in administrator into submitting a crafted request that changes the plugin's settings (stored via update_option()), such as the display style used to render the PageRank badge.

NVD CVE-2026-6294Wordfence 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):
Google PageRank Display vulnerability status badge
<a href="https://laskyr.com/plugins/google-pagerank-display"><img src="https://laskyr.com/plugins/google-pagerank-display/badge.svg" alt="Google PageRank Display 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