# CVE-2026-122670: WP SYNTEX Polylang broken access control in pages

Source: https://junglewise.ai/threats/cve-2026-122670-missing-authorization-vulnerability-in-wp-syntex-polylang  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-06. Updated: 2026-11-06  
License: CC BY 4.0 with a link back

CVE-2026-122670 · Severity: medium · CVSS 5.4 · Published 2026-11-06

Polylang is a WordPress plugin that enables multilingual websites. A broken access control vulnerability allows users with contributor or developer permissions to access pages and perform actions they should not be authorized to perform, potentially viewing other users' data or modifying site content beyond their role.

Technologies: [WP SYNTEX Polylang](https://junglewise.ai/threats/technologies/polylang). Vendors: [WP SYNTEX](https://junglewise.ai/threats/vendors/wp-syntex).

## Quick answers

**Is CVE-2026-122670 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-122670 being exploited in the wild.

**How severe is CVE-2026-122670?** Medium severity, with a CVSS score of 5.4, published 6 November 2026.

**Which products and versions are affected?** WP SYNTEX Polylang through 3.9.

**Is there a fix for CVE-2026-122670?** Yes: fixed in 3.9.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-122670 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-122670?** Check whether you run WP SYNTEX Polylang at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 3.9.1

## Technical details

The vulnerability is a broken access control issue (CWE-284) in Polylang plugin versions up to 3.9. An attacker with contributor or developer privileges can bypass authorization checks to access or modify pages. The vulnerability requires authentication and an existing user account with at least contributor-level permissions to exploit.

## Affected products

- WP SYNTEX Polylang through 3.9

## Timeline

- 2026-10-25: disclosed
- 2026-11-06: advisory
- 2026-11-06: patched

## References

- [https://wordpress.org/plugins](https://wordpress.org/plugins)
- [https://patchstack.com/database/wordpress/plugin/polylang/vulnerability/wordpress-polylang-plugin-3-9-broken-access-control-vulnerability?_s_id=cve](https://patchstack.com/database/wordpress/plugin/polylang/vulnerability/wordpress-polylang-plugin-3-9-broken-access-control-vulnerability?_s_id=cve)

## Related threats

- [WP SYNTEX Polylang object injection in deserialization](https://junglewise.ai/threats/cve-2026-97278-deserialization-of-untrusted-data-vulnerability-in-wp-syntex)
- [WP SYNTEX Polylang missing authorization in data retrieval](https://junglewise.ai/threats/cve-2026-39783-missing-authorization-vulnerability-in-wp-syntex-polylang)
- [Polylang stored cross-site scripting in contributor roles](https://junglewise.ai/threats/cve-2026-97279-contributor-cross-site-scripting-xss-in-polylang-3-8-9-versions)
- [Chouby Polylang sensitive data exposure](https://junglewise.ai/threats/cve-2026-65458-chouby-polylang-sensitive-data-exposure)