CVE-2026-22462
BaseFortify
Publication date: 2026-01-22
Last updated on: 2026-01-27
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| richardevcom | add_polylang_support_for_customizer | to 1.4.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-22462 is a Cross Site Request Forgery (CSRF) vulnerability in the WordPress plugin "Add Polylang support for Customizer" versions up to and including 1.4.5. It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions by having them click a malicious link, visit a crafted page, or submit a form. The vulnerability requires user interaction and does not affect unauthenticated users directly. [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized actions being performed on your WordPress site by privileged users without their intention, potentially compromising site settings or functionality. However, exploitation is considered unlikely due to the low severity (CVSS score 4.3) and the requirement for user interaction. No official fix or patch is currently available. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this CSRF vulnerability involves monitoring for suspicious user interactions that could trigger unwanted actions in the Add Polylang support for Customizer plugin (versions <= 1.4.5). Since the vulnerability requires privileged user interaction (such as clicking a malicious link or submitting a crafted form), network detection could focus on unusual HTTP requests or referrers targeting the plugin's endpoints. However, no specific detection commands or signatures are provided. It is recommended to audit user activity logs and web server logs for unexpected POST requests related to the plugin. No official detection commands are available. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the plugin's functionality to only trusted users, educating users about the risks of clicking unknown links, and implementing additional CSRF protections such as tokens or user interaction confirmations if possible. Since no official fix or patched version is currently available, consider disabling or removing the Add Polylang support for Customizer plugin until a patch is released. Monitoring and limiting privileged user actions can reduce the risk of exploitation. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.