Title: Modified plugin file: wp-content/plugins/wordpress-seo/admin/class-pointers.php
Last modified: August 30, 2016

---

# Modified plugin file: wp-content/plugins/wordpress-seo/admin/class-pointers.php

 *  Resolved [RalphGL](https://wordpress.org/support/users/ralphgl/)
 * (@ralphgl)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/)
 * First: Thank you for your useful plugin!
 * But please, don´t change things in your sourcecode without changing the version
   number. Security tools, like the “Wordfence” Plugin check if the source of a 
   plugin and the local source on the server are different. And they send alerts
   because there are distinctions in actual 2.2.1 to the version 2.2.1 i have downloaded
   a some times ago.
 * For example:
    in class-pointers.php line 249 was: . ‘<form action=”[http://yoast.us1.list-manage1.com/subscribe/post?u=ffa93edfe21752c921f860358&id=972f1c9122&#8243](http://yoast.us1.list-manage1.com/subscribe/post?u=ffa93edfe21752c921f860358&id=972f1c9122&#8243);
   method=”post” selector=”newsletter-form” accept-charset=”‘ . esc_attr( get_bloginfo(‘
   charset’ ) ) . ‘”>’ and now line 249 is: . ‘<form action=”[http://yoast.us1.list-manage1.com/subscribe/post?u=ffa93edfe21752c921f860358&selector=972f1c9122&#8243](http://yoast.us1.list-manage1.com/subscribe/post?u=ffa93edfe21752c921f860358&selector=972f1c9122&#8243);
   method=”post” selector=”newsletter-form” accept-charset=”‘ . esc_attr( get_bloginfo(‘
   charset’ ) ) . ‘”>’
 * I think even small changes on the sourcecode should get a new version number 
   to avoid such false positives.
 * Best regards
    Ralph
 * [https://wordpress.org/plugins/wordpress-seo/](https://wordpress.org/plugins/wordpress-seo/)

Viewing 15 replies - 1 through 15 (of 16 total)

1 [2](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/page/2/?output_format=md)

 *  [elirnerak](https://wordpress.org/support/users/karenrilegmailcom/)
 * (@karenrilegmailcom)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306811)
 * I agree: everyone who uses your plugin and also uses Wordfence received an alert
   this morning.
 *  [fritz.barnes](https://wordpress.org/support/users/fritzbarnes/)
 * (@fritzbarnes)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306818)
 * Yep. Ten thousand people (I made up the number, but obviously it is a lot) around
   the world have to research this issue. Your company does so many things well….
   and we all appreciate it…just think your code release procedure should be tightened
   up a bit in this regard.
 *  [Larryhir](https://wordpress.org/support/users/larryhir/)
 * (@larryhir)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306821)
 * Ditto…got this on multiple sites. Glad wordfence works, unnecessary panic.
 *  [kevin@nolka.com](https://wordpress.org/support/users/kevinnolkacom/)
 * (@kevinnolkacom)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306829)
 * I got this too on my WordPress sites using Wordfence – just to confirm – is there
   anything to be alarmed about?
 *  [michaelmartinezcampos](https://wordpress.org/support/users/michaelmartinezcampos/)
 * (@michaelmartinezcampos)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306869)
 * Another concerned user here. Please confirm that this was an intentional change.
   I have the plugin running on a production site.
 *  [homerecords](https://wordpress.org/support/users/homerecords/)
 * (@homerecords)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306873)
 * Same warning here and I compared the line with same file in version 2.2.1 and
   there it also says: amp;selector=972f1c9122 and not id=972f1c9122.
 * So I uploaded the latest class-pointers.php and everything seems fine.
 *  [kevin@nolka.com](https://wordpress.org/support/users/kevinnolkacom/)
 * (@kevinnolkacom)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306912)
 * Hi homerecords
    Where did you get the “latest class-pointers.php” from? Kevin.
 *  [fritz.barnes](https://wordpress.org/support/users/fritzbarnes/)
 * (@fritzbarnes)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306916)
 * Kevin, if you have Wordfence, I think there is an option to just replace the 
   file.
 *  [frankb75](https://wordpress.org/support/users/frankb75/)
 * (@frankb75)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306921)
 * I reverted the plugin changes using WordFence because of the error. I wasn’t 
   sure if it has a compromised file. I echo the sentiments above.
 *  Thread Starter [RalphGL](https://wordpress.org/support/users/ralphgl/)
 * (@ralphgl)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306935)
 * The Wordfence guys think changed code should have a new version number, and i
   think they are right.
 * [@fritz](https://wordpress.org/support/users/fritz/).barnes Wordfence allow to
   replace the changed file (in this case the older one) to the original file (in
   this case the newer one).
    But if wordfence – for whatever reason – does not 
   identify all changes of a different version with the same version number the 
   chaos will be perfect.
 * A better workaround IMHO could be a reinstall of all files by ftp.
    But, hey 
   [@guys](https://wordpress.org/support/users/guys/) at yoast – this is not the
   way we love to work with WordPress.
 * Best practise should be: if soemone changes (even changes in an included library)
   a new version number is assigned.
 *  [OviLiz](https://wordpress.org/support/users/ovib/)
 * (@ovib)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306941)
 * No official answer… 🙁
 *  [dmac](https://wordpress.org/support/users/darrenmcentee/)
 * (@darrenmcentee)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306951)
 * I reached out to them on twitter also, no answer, yet.
 *  [michaelmartinezcampos](https://wordpress.org/support/users/michaelmartinezcampos/)
 * (@michaelmartinezcampos)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306960)
 * we demand ANSWERS! 🙂
 *  [Taco Verdonschot](https://wordpress.org/support/users/tacoverdo/)
 * (@tacoverdo)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6306965)
 * Thanks for your tweet Darren.
 * The reason for the minor edit is a change by MailChimp that caused the newsletter
   signup in the tour to fail (404 error).
 * This is no reason to update your plugin at all, but it is something we want changed
   for our new users. Therefore we updated a single line, without changing the version
   number.
    So yes, this was an intentional change.
 * If you’re using WordFence, you can have WordFence update the file to get rid 
   of the ‘false positive’.
 *  [homerecords](https://wordpress.org/support/users/homerecords/)
 * (@homerecords)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/#post-6307017)
 * @ [kevin@nolka.com](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/kevin@nolka.com?output_format=md):
 * I used the file from the latest plugin download.

Viewing 15 replies - 1 through 15 (of 16 total)

1 [2](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/page/2/?output_format=md)

The topic ‘Modified plugin file: wp-content/plugins/wordpress-seo/admin/class-pointers.
php’ is closed to new replies.

 * ![](https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908)
 * [Yoast SEO - Advanced SEO with real-time guidance and built-in AI](https://wordpress.org/plugins/wordpress-seo/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-seo/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-seo/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-seo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-seo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-seo/reviews/)

## Tags

 * [alert](https://wordpress.org/support/topic-tag/alert/)
 * [file change](https://wordpress.org/support/topic-tag/file-change/)

 * 16 replies
 * 11 participants
 * Last reply from: [OviLiz](https://wordpress.org/support/users/ovib/)
 * Last activity: [10 years, 8 months ago](https://wordpress.org/support/topic/modified-plugin-file-wp-contentpluginswordpress-seoadminclass-pointersphp/page/2/#post-6307047)
 * Status: resolved