CVE-2023-35041

Webpushr <= 4.34.0 - Cross-Site Request Forgery to Local File Inclusion via menu

2023-10-19 00:00
Theodoros Malachias

Strategic Overview

Status
Patched in 4.35.0
Affected Version
<= 4.34.0
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-35041
View all Web Push Notifications – Webpushr vulnerabilities

At a glance

CVE-2023-35041 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Web Push Notifications WordPress plugin, affecting versions <= 4.34.0. 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.35.0; sites on affected versions should update now. Disclosed October 2023, reported by Theodoros Malachias.

Vulnerability Overview

The Webpushr plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.34.0. This is due to missing or incorrect nonce validation within the wpp_save_settings function. This makes it possible for unauthenticated attackers to conduct local file inclusion attacks by leveraging the 'menu' parameter 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)

Web Push Notifications <= 4.34.0 carries this weakness at menu, 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 Web Push Notifications the fix is 4.35.0: builds <= 4.34.0 are affected, anything from 4.35.0 onward is not.

Remediation

Update to version 4.35.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Web Push Notifications: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Web Push Notifications 4.35.0 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