CVE-2022-30337

WP Meta SEO <= 4.4.8 - Cross-Site Request Forgery to Settings Update

2022-06-22 00:00
Anonymous

Strategic Overview

Status
Patched in 4.4.9
Affected Plugin
WP Meta SEO
Affected Version
<= 4.4.8
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-30337
View all WP Meta SEO vulnerabilities

At a glance

CVE-2022-30337 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Meta SEO WordPress plugin, affecting versions <= 4.4.8. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.4.9; sites on affected versions should update now. Disclosed June 2022.

Vulnerability Overview

The WP Meta SEO plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.4.8. This is due to incorrect nonce validation which only verifies the presence of a nonce value rather than the on the validity of the nonce on a couple of cases in the loadPage() function. This makes it possible for unauthenticated attackers to modify the plugin's settings 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

WP Meta SEO <= 4.4.8 carries this weakness at loadPage(), and reaching it 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 WP Meta SEO the fix is 4.4.9: builds <= 4.4.8 are affected, anything from 4.4.9 onward is not.

Remediation

Update to version 4.4.9, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-30337https://www.wordfence.com/threat-intel/vulnerabilities/id/69c7b0e4-89bf-480c-8e89-b1514d2bfefehttps://nvd.nist.gov/vuln/detail/CVE-2022-30337

Related records

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