WPGlobus vulnerabilities

Plugin slug wpglobus · 7 known vulnerabilities · latest disclosed 2018-01-11 · WordPress.org page

Every listed vulnerability has a fix. Version 1.9.7 or later is not affected by any of them. If your site runs an older version, update it.

1 of 7 rated high or critical (CVSS 7 or more).

Known vulnerabilities in WPGlobus

SeverityAffected versionsFixed inCVEPublishedDetails
High 8.8<= 1.9.61.9.7CVE-2018-53612018-01-11Advisory
Medium 4.8<= 1.9.61.9.7CVE-2018-53662018-01-11Advisory
Medium 6.1<= 1.9.61.9.7CVE-2018-53652018-01-11Advisory
Medium 4.8<= 1.9.61.9.7CVE-2018-53672018-01-11Advisory
Medium 4.8<= 1.9.61.9.7CVE-2018-53632018-01-11Advisory
Medium 4.8<= 1.9.61.9.7CVE-2018-53642018-01-11Advisory
Medium 4.8<= 1.9.61.9.7CVE-2018-53622018-01-11Advisory

Check if a site is affected

Enter a site address to see which version of WPGlobus and other plugins it runs, and whether they match a known vulnerability.

Questions

Is the WPGlobus plugin safe to use?

All 7 known issues are fixed in current versions (1.9.7 or later). Keeping it updated is what matters.

How do I check which version of WPGlobus my site runs?

In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.

How do I fix a vulnerable plugin?

Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.

Check any WordPress site in one click while you browse: Add PluginPeek to Chrome