Security readout for executives and security teams
Plain-English summary
This WordPress plugin flaw lets an unauthenticated visitor change Polylang-related theme and plugin translation settings and import translation strings. That can disrupt site language behavior or alter displayed translation content, but the supplied sources do not indicate data theft or confirmed active exploitation.
Executive priority
Treat this as a moderate-priority WordPress hygiene issue. It is not shown as actively exploited, but unauthenticated modification risk justifies prompt inventory and upgrade or removal on public sites.
Technical view
CVE-2022-4169 is a missing authorization issue in Theme and plugin translation for Polylang through 3.2.16. The vulnerable process_polylang_theme_translation_wp_loaded() path lacked capability checks, allowing unauthenticated modification of translation settings and import of strings. CVSS is 6.5, CWE-862.
Likely exposure
Exposure is likely limited to WordPress sites running Theme and plugin translation for Polylang at version 3.2.16 or earlier. Sites not using this plugin, or using a non-vulnerable version, are not indicated as affected by the supplied sources.
Exploitation context
The vulnerability is network-accessible, low-complexity, and needs no login or user interaction. CISA KEV status is false in the bundle, and the supplied sources do not show confirmed active exploitation.
Researcher notes
The key issue is absent capability enforcement in process_polylang_theme_translation_wp_loaded(). Public evidence supports authorization bypass with low integrity and availability impact, not confidentiality impact. The bundle does not provide exploit telemetry beyond KEV=false.
Mitigation direction
- Identify all WordPress sites using Theme and plugin translation for Polylang.
- Upgrade beyond version 3.2.16 where vendor guidance provides a fixed release.
- Disable or remove the plugin if it is not required.
- Review vendor and Wordfence guidance before relying on compensating controls.
- Monitor translation settings and imported strings for unexpected changes.
Validation and detection
- Check the installed plugin version on each WordPress site.
- Confirm whether Theme and plugin translation for Polylang is active.
- Review recent translation settings for unauthorized changes.
- Check recent imported translation strings for unexpected content.
- Verify remediation against vendor release notes or WordPress plugin changelog.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-4169 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9f6a358a-333c-4eb7-9149-348bf3713943?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=2814605%40theme-translation-for-polylang%2Ftrunk&old=2812254%40theme-translation-for-polylang%2Ftrunk&sfp_email=&sfph_mail=CVE reference
- https://www.wordfence.com/vulnerability-advisories-continued/#CVE-2022-4169CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.