LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22462: WordPress Add Polylang support for Customizer plugin <= 1.4.5 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in richardevcom Add Polylang support for Customizer add-polylang-support-for-customizer allows Cross Site Request Forgery.This issue affects Add Polylang support for Customizer: from n/a through <= 1.4.5.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22462 is a CSRF flaw in the WordPress plugin Add Polylang support for Customizer through version 1.4.5. An attacker could trick a logged-in site user into causing an unintended action, creating limited integrity risk. It is not listed as actively exploited in the provided sources.

Executive priority

Treat as a routine WordPress plugin remediation item. Prioritize affected public websites and administrative environments, but this is not currently evidenced as a crisis-level issue or actively exploited vulnerability.

Technical view

The issue is CWE-352 Cross-Site Request Forgery affecting richardevcom Add Polylang support for Customizer <= 1.4.5. CVSS 3.1 is 4.3, vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. The impact is limited to integrity; confidentiality and availability impacts are not indicated.

Likely exposure

Exposure is limited to WordPress sites with the Add Polylang support for Customizer plugin installed at version 1.4.5 or earlier. Sites not using this plugin are not exposed based on the provided sources.

Exploitation context

Exploitation requires user interaction, consistent with CSRF. The attacker does not need prior privileges, but the victim must be induced to perform an action. No KEV listing or cited source in the bundle confirms active exploitation.

Researcher notes

The public data identifies the weakness class and affected version range but does not provide detailed vulnerable functionality or a named fixed version in the supplied bundle. Avoid assuming exploitability beyond CSRF with required user interaction and low integrity impact.

Mitigation direction

  • Inventory WordPress sites for the affected plugin and version.
  • If version is <= 1.4.5, check vendor or Patchstack guidance for an update.
  • Disable or remove the plugin if it is unnecessary.
  • Apply least-privilege practices for WordPress administrative users.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record the installed plugin version.
  • Flag versions 1.4.5 or earlier for remediation review.
  • Review vendor, CVE, and Patchstack pages for updated fix information.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookup
cve · low confidence lookup

CVE-2026-22462 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-22462Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
richardevcomAdd Polylang support for Customizeradd-polylang-support-for-customizer, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.