Polylang vulnerability records, and the language settings a version cannot show
Polylang gives posts, terms and strings a language and sets that language from the address.
Its records are named here by CVE id, beside the places a version number cannot reach: the languages table, the URL modification module and what the pll/v1 REST routes return to a signed-out browser.
On this page
Polylang vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 8 records for Polylang. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 3.9.1
Worked out from data retrieved on .
Every affected range listed in this source for Polylang ends before version 3.9.1.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Polylang <= 3.9 - Missing Authorization
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2026-122670
Affected versions- All versions up to and including 3.9
Patched versions: 3.9.1
Update to at least version 3.9.1.
Polylang <= 3.8.9 - Authenticated (Editor+) PHP Object Injection
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.6)
- CVE:
- CVE-2026-97278
Affected versions- All versions up to and including 3.8.9
Patched versions: 3.8.10
Update to at least version 3.8.10.
Polylang <= 3.8.7 - Authenticated (Contributor+) Information Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2026-39783
Affected versions- All versions up to and including 3.8.7
Patched versions: 3.8.8
Update to at least version 3.8.8.
Polylang <= 3.8.9 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-97279
Affected versions- All versions up to and including 3.8.9
Patched versions: 3.8.10
Update to at least version 3.8.10.
Polylang <= 3.8.5 - Authenticated (Contributor+) Sensitive Information Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2026-65458
Affected versions- All versions up to and including 3.8.5
Patched versions: 3.8.6
Update to at least version 3.8.6.
Show 3 older recordsHide the older records
Polylang <= 3.7.3 - Authenticated (Contributor+) PHP Object Injection
- Published:
- Last updated:
- Severity:
- High (CVSS 7.5)
- CVE:
- CVE-2025-64353
Affected versions- All versions up to and including 3.7.3
Patched versions: 3.7.4
Update to at least version 3.7.4.
Polylang <= 2.5 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- High (CVSS 8.8)
Affected versions- All versions before 2.5.1
Patched versions: 2.5.1
Update to at least version 2.5.1.
Polylang <= 1.5.1 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.1)
- CVE:
- CVE-2014-4855
Affected versions- All versions before 1.5.2
Patched versions: 1.5.2
Update to at least version 1.5.2.
Check Polylang on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What Polylang translates and where it takes input
Polylang is published on WordPress.org by Chouby.
The features its listing names include translating posts, pages, media, categories, post tags, custom post types and taxonomies, and the listing describes two further plugins: Polylang Pro, whose extras include machine translation with DeepL and XLIFF export and import, and Polylang for WooCommerce, an add-on.
One of the listing's screenshots is captioned "The Edit Post screen with the Languages metabox". The languages guide adds languages at Languages > Languages. Strings such as the site title, the tagline and text generally held in theme and plugin options are translated at Languages > Translations, which the strings translation guide says only the Administrator can access.
What the Polylang vulnerability records show
The titles named here include PHP object injection, information exposure, stored cross-site scripting and cross-site request forgery.
Of those quoted, two state "(Contributor+)" and one "(Editor+)"; the titles of CVE-2026-122670 and the 16 Jan 2019 record carry no access wording.
- CVE-2026-122670, published 6 Nov 2026. Affected: all versions up to and including 3.9. Patched versions: 3.9.1.
- CVE-2026-97278 has a title ending "Authenticated (Editor+) PHP Object Injection". Affected: all versions up to and including 3.8.9. Patched versions: 3.8.10.
- CVE-2026-97279 has a title ending "Authenticated (Contributor+) Stored Cross-Site Scripting". Affected: all versions up to and including 3.8.9. Patched versions: 3.8.10.
- CVE-2026-39783 has a title ending "Authenticated (Contributor+) Information Exposure". Affected: all versions up to and including 3.8.7. Patched versions: 3.8.8.
- A record published on 16 Jan 2019 without a CVE id has a title ending "Cross-Site Request Forgery", and the history gives its severity as High (CVSS 8.8). Affected: all versions before 2.5.1. Patched versions: 2.5.1.
Where the Polylang 3.8 ranges overlap
CVE-2026-39783 lists 3.8.8 in its patched versions field, while the affected ranges of CVE-2026-97278 and CVE-2026-97279 run up to and including 3.8.9, so a copy on 3.8.8 is outside the first record and inside the other two.
The title of the 16 Jan 2019 record begins "Polylang <= 2.5", while its affected field reads all versions before 2.5.1. Where a title and its fields differ, go by the fields.
Polylang's changelog on the WordPress.org listing begins its security lines with "Security:", so the entries for releases after the installed version are worth reading as well as this history.
Where to read each Polylang check
Use the checklist on this page only on a site you are authorised to review.
Sign in as an administrator and read without changing anything: the languages guide says clicking the star that appears when you hover over a language row changes the default language, so leave the star alone and leave every settings screen without saving.
Copy the Polylang version from its Description column on the Plugins screen, note the date and whether the screen shows an update notice for it, and give any Polylang Pro or Polylang for WooCommerce row a line of its own. The vendor's installation page says the two versions of Polylang cannot be active at the same time and that activating Polylang Pro deactivates Polylang, so note which row is active.
The same page has Pro and the add-on installed from ZIP files downloaded from the vendor. For plugins installed that way, WordPress's guide to the Plugins screen says an update notice shows there only when the plugin's author has built in an updater.
At Languages > Languages, write down each language's name, locale and language code, and which one carries the star that marks the default. The languages guide says the language code is used in the URL when the language is set from the directory name.
Then record who can change them, starting with the accounts the Administrator filter link on the Users screen lists. For Polylang Pro 3.8 or later, the capabilities guide adds manage_languages (the languages table and its REST API), manage_translations (the Translations table, without full administrator rights), machine_translate (DeepL) and a capability restricting a role to one language.
The guide writes that last one three ways: translate_ plus the language slug in its table, language_ plus the slug (language_it for Italian) as the capability name in its section on restricting users, and translate_it in that section's steps.
It assigns them with the User Role Editor plugin at Users > User Roles Editor; where that plugin is installed, note which roles hold each one without clicking Update.
The URL modifications guide puts these options in the URL modification module under Languages > Settings. Record how the language is set: from a code in the address such as ?lang=fr, the default with plain permalinks; from the directory name, the default with pretty permalinks; or, also with pretty permalinks, from subdomains or a domain per language.
Then note whether the code is hidden for the default language, whether /language/ stays in archive URLs, and, where a static front page is used, whether its URL holds the language code instead of the page name or page ID.
Under Languages > Settings, the Custom post types and Taxonomies module lists post types and taxonomies with checkboxes that choose whether languages and translation management are enabled for each. Record which are ticked; the guide notes that by default only those registered as public are listed.
On Polylang Pro, the languages guide says a deactivated language is hidden from visitors and subscribers on the front end but remains visible in the admin to logged-in users with the edit_posts capability, such as administrators, editors, authors and contributors. Note any deactivated language.
At Languages > Translations, with the filters on "View all groups" and "Show all languages", record which groups appear. The strings translation guide lists a WordPress group with the site title, tagline, date format and time format, a widget group once widgets are set up, a URL slugs group whose slugs need Polylang Pro to translate, and groups that plugins and themes add.
The Languages REST API page says that API has been included with Polylang since 3.7, at /wp-json/pll/v1/languages, and the Settings REST API page puts settings at /wp-json/pll/v1/settings; both say changes need the manage_options capability. A page headed REST API, bannered as available only in Polylang Pro, lists the same languages endpoint.
In a browser window that is not signed in, open both pll/v1 addresses and write down the status and fields each returns. Compare the languages listed with the Languages screen, noting each one's active value where it appears, since the Languages REST API page says deactivated languages are also listed.
Check whether the settings response includes machine_translation_services, which the settings page lists as a Pro setting for the DeepL API key and formality. Send nothing but these address-bar requests.
What a Polylang version match cannot show
A Polylang version inside an affected range means a known record covers that copy.
It cannot tell you whether the flaw was ever exploited, or how the plugin is configured: which roles hold manage_translations, whether wp-config.php sets PLL_ENABLE_MACHINE_TRANSLATION_CAPABILITIES, which the capabilities guide requires before machine_translate controls DeepL access, or what the pll/v1 routes return to a signed-out browser.
A WordPress security audit calls each REST route under /wp-json/ without a session and treats one that returns personal information or settings to an anonymous request as a finding.
Frequently asked questions
The languages guide says a language deactivated in Polylang Pro is hidden from visitors and subscribers on the front end. The Languages REST API page says GET /wp-json/pll/v1/languages lists deactivated languages as well and requires manage_options when the request is made with context set to edit, and it names active among the properties of a language object. Compare what a signed-out browser receives there with the Languages screen.
Every record here is one the source data files under the polylang slug, and where a record is filed does not show whether it also applies to Polylang Pro or the WooCommerce add-on. The vendor's installation page has the free version installed from the WordPress.org repository and the other two from their own ZIP files, and says activating Polylang Pro deactivates Polylang.
The URL modifications guide notes, under the directory-name option, that if Polylang is deactivated, URLs lose their language information and all external links are broken. That option is the default with pretty permalinks, so record the URL mode before planning any step that deactivates the plugin.
The strings translation guide says they are stored in the database as the polylang_mo post type in the wp_posts table. When a theme or plugin is deactivated, the translations of its options stay there although the Translations table stops showing them, and the guide's "Clean strings translation database" option deletes them permanently once changes are saved.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 7 of the 8 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Polylang <= 3.9 - Missing Authorization (CVE-2026-122670)
- Polylang <= 3.8.9 - Authenticated (Editor+) PHP Object Injection (CVE-2026-97278)
- Polylang <= 3.8.7 - Authenticated (Contributor+) Information Exposure (CVE-2026-39783)
- Polylang <= 3.8.9 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2026-97279)
- Polylang <= 3.8.5 - Authenticated (Contributor+) Sensitive Information Exposure (CVE-2026-65458)
- Polylang <= 3.7.3 - Authenticated (Contributor+) PHP Object Injection (CVE-2025-64353)
- Polylang <= 2.5 - Cross-Site Request Forgery
- Polylang <= 1.5.1 - Cross-Site Scripting (CVE-2014-4855)