Polylang vulnerabilities

Plugin slug polylang · 8 known vulnerabilities · latest disclosed 2026-11-06 · WordPress.org page

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

3 of 8 rated high or critical (CVSS 7 or more).

Known vulnerabilities in Polylang

SeverityAffected versionsFixed inCVEPublishedDetails
Medium 4.3<= 3.93.9.1CVE-2026-1226702026-11-06Advisory
Medium 6.6<= 3.8.93.8.10CVE-2026-972782026-10-12Advisory
Medium 4.3<= 3.8.73.8.8CVE-2026-397832026-10-05Advisory
Medium 6.4<= 3.8.93.8.10CVE-2026-972792026-09-30Advisory
Medium 4.3<= 3.8.53.8.6CVE-2026-654582026-07-22Advisory
High 7.5<= 3.7.33.7.4CVE-2025-643532025-10-28Advisory
High 8.8< 2.5.12.5.1none2019-01-16Advisory
High 7.1< 1.5.21.5.2CVE-2014-48552014-08-01Advisory

Check if a site is affected

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

Questions

Is the Polylang plugin safe to use?

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

How do I check which version of Polylang 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