Polylang at a glance
- 8 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Nov 6, 2026.
- Ranked #70 by popularity on WordPress.org (900,000+ active installs).
- The latest version is 3.9.2 (released Nov 9, 2026). The most recent security fix shipped in 3.9.1.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Polylang version
Enter the Polylang version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Polylang”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Polylang”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (3.9.2). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Polylang vulnerabilities
Polylang <= 3.9 - Missing Authorization
Missing authorization · CVE-2026-122670
Affected versions: ≤ 3.9
Fixed in: 3.9.1
Severity: Medium 4.3 · Disclosed Nov 6, 2026
Polylang <= 3.8.9 - Authenticated (Editor+) PHP Object Injection
PHP object injection · CVE-2026-97278
Affected versions: ≤ 3.8.9
Fixed in: 3.8.10
Severity: Medium 6.6 · Disclosed Oct 12, 2026
Polylang <= 3.8.7 - Authenticated (Contributor+) Information Exposure
Information disclosure · CVE-2026-39783
Affected versions: ≤ 3.8.7
Fixed in: 3.8.8
Severity: Medium 4.3 · Disclosed Oct 5, 2026
Polylang <= 3.8.9 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-97279
Affected versions: ≤ 3.8.9
Fixed in: 3.8.10
Severity: Medium 6.4 · Disclosed Sep 30, 2026
Polylang <= 3.8.5 - Authenticated (Contributor+) Sensitive Information Exposure
Information disclosure · CVE-2026-65458
Affected versions: ≤ 3.8.5
Fixed in: 3.8.6
Severity: Medium 4.3 · Disclosed Jul 22, 2026
Polylang <= 3.7.3 - Authenticated (Contributor+) PHP Object Injection
PHP object injection · CVE-2025-64353
Affected versions: ≤ 3.7.3
Fixed in: 3.7.4
Severity: High 7.5 · Disclosed Oct 28, 2025
Polylang <= 2.5 - Cross-Site Request Forgery
Cross-site request forgery (CSRF)
Affected versions: < 2.5.1
Fixed in: 2.5.1
Severity: High 8.8 · Disclosed Jan 16, 2019
Polylang <= 1.5.1 - Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2014-4855
Affected versions: < 1.5.2
Fixed in: 1.5.2
Severity: High 7.1 · Disclosed Aug 1, 2014
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Polylang <= 3.9 - Missing AuthorizationMissing authorization · CVE-2026-122670 | ≤ 3.9 | 3.9.1 | Medium 4.3 | Nov 6, 2026 |
| Polylang <= 3.8.9 - Authenticated (Editor+) PHP Object InjectionPHP object injection · CVE-2026-97278 | ≤ 3.8.9 | 3.8.10 | Medium 6.6 | Oct 12, 2026 |
| Polylang <= 3.8.7 - Authenticated (Contributor+) Information ExposureInformation disclosure · CVE-2026-39783 | ≤ 3.8.7 | 3.8.8 | Medium 4.3 | Oct 5, 2026 |
| Polylang <= 3.8.9 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-97279 | ≤ 3.8.9 | 3.8.10 | Medium 6.4 | Sep 30, 2026 |
| Polylang <= 3.8.5 - Authenticated (Contributor+) Sensitive Information ExposureInformation disclosure · CVE-2026-65458 | ≤ 3.8.5 | 3.8.6 | Medium 4.3 | Jul 22, 2026 |
| Polylang <= 3.7.3 - Authenticated (Contributor+) PHP Object InjectionPHP object injection · CVE-2025-64353 | ≤ 3.7.3 | 3.7.4 | High 7.5 | Oct 28, 2025 |
| Polylang <= 2.5 - Cross-Site Request ForgeryCross-site request forgery (CSRF) | < 2.5.1 | 2.5.1 | High 8.8 | Jan 16, 2019 |
| Polylang <= 1.5.1 - Cross-Site ScriptingCross-site scripting (XSS) · CVE-2014-4855 | < 1.5.2 | 1.5.2 | High 7.1 | Aug 1, 2014 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 6, 2026.
Most common weaknesses in Polylang
PHP object injection
2 issues
Specially crafted data makes the server behave in unintended ways. Combined with the right conditions, it can lead to a full takeover.
Information disclosure
2 issues
Data that should stay private, such as user details or configuration values, can be read from outside.
Cross-site scripting (XSS)
2 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Frequently asked questions
Is Polylang safe to use?
Polylang is a well-known plugin with 900,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.9.2) and turn on automatic updates.
How do I find which version of Polylang my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.