CVE-2023-5620

Webpushr <= 4.34.0 - Missing Authorization to Unauthenticated Stored Cross-Site Scripting

2023-11-06 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 4.35.0
Affected Version
<= 4.34.0
CVSS
7.2High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-5620
View all Web Push Notifications – Webpushr vulnerabilities

At a glance

CVE-2023-5620 is a high-severity Missing Authorization vulnerability in the Web Push Notifications WordPress plugin, affecting versions <= 4.34.0. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.35.0; sites on affected versions should update now. Disclosed November 2023, reported by Krzysztof Zając.

Vulnerability Overview

The Web Push Notifications – Webpushr plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wpp_save_settings function in all versions up to, and including, 4.34.0. This makes it possible for unauthenticated attackers to modify plugin options and inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Web Push Notifications <= 4.34.0 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. 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?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. 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.

  • Login Security
  • Alerts

External References

Related records

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