CVE-2023-37968

Falang multilanguage <= 1.3.39 - Cross-Site Request Forgery via add_language

2023-07-12 00:00
Skalucy

Strategic Overview

Status
Patched in 1.3.40
Affected Version
<= 1.3.39
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-37968
View all Falang multilanguage for WordPress vulnerabilities

At a glance

CVE-2023-37968 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Falang multilanguage for WordPress WordPress plugin, affecting versions <= 1.3.39. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.3.40; sites on affected versions should update now. Disclosed July 2023, reported by Skalucy.

Vulnerability Overview

The Falang multilanguage plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.39. This is due to missing or incorrect nonce validation on the add_language, update_language, and delete_language functions. This makes it possible for unauthenticated attackers to invoke those functions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Falang multilanguage for WordPress <= 1.3.39 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Falang multilanguage for WordPress the fix is 1.3.40: builds <= 1.3.39 are affected, anything from 1.3.40 onward is not.

Remediation

Update to version 1.3.40, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Falang multilanguage for WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Falang multilanguage for WordPress 1.3.40 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C