Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesPolylang

Polylang vulnerabilities

Polylang has 4 known vulnerabilities in this database. The most recent published record is dated 6 Nov 2026.

Known vulnerabilities
4
Active installs
900,000+
Latest version
3.9.1
Last updated
21 Oct 2026
Most recent
6 Nov 2026

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
Broken access control
CVE-2026-122670
Medium 5.4Up to 3.9Fixed in a later version (latest 3.9.1)6 Nov 2026
PHP object injection
CVE-2026-97278
High 7.2Up to 3.8.9Fixed in a later version (latest 3.9.1)14 Oct 2026
Broken access control
CVE-2026-39783
Medium 4.3Up to 3.8.7Fixed in a later version (latest 3.9.1)5 Oct 2026
Cross-site scripting (XSS)
CVE-2014-4855
Not scoredUp to 1.5.1Fixed in a later version (latest 3.9.1)10 Jul 2014
Read the published descriptions
CVE-2026-122670, 6 Nov 2026
Missing Authorization vulnerability in WP SYNTEX Polylang polylang allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Polylang: from n/a through 3.9. CVE record
CVE-2026-97278, 14 Oct 2026
Deserialization of Untrusted Data vulnerability in WP SYNTEX Polylang polylang allows Object Injection.This issue affects Polylang: from n/a through 3.8.9. CVE record
CVE-2026-39783, 5 Oct 2026
Missing Authorization vulnerability in WP SYNTEX Polylang polylang allows Retrieve Embedded Sensitive Data.This issue affects Polylang: from n/a through 3.8.7. CVE record
CVE-2014-4855, 10 Jul 2014
Cross-site scripting (XSS) vulnerability in the Polylang plugin before 1.5.2 for WordPress allows remote attackers to inject arbitrary web script or HTML via vectors related to a user description. NOTE: some of these details are obtained from third party information. CVE record

What to do if you run Polylang

If you run Polylang, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.

If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.

Email me about new Polylang vulnerabilities

Free. We email you when a new vulnerability is published for Polylang, usually within minutes. Confirm by email; unsubscribe any time.

Focus on your business. We’ll take care of your website.

From everyday updates to ongoing care, we keep your website working.

Get website support