CVE-2023-48277

Super Progressive Web Apps <= 2.2.21 - Missing Authorization

2023-11-22 00:00
Abdi Pranata

Strategic Overview

Status
Patched in 2.2.22
Affected Version
<= 2.2.21
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-48277
View all Super Progressive Web Apps vulnerabilities

At a glance

CVE-2023-48277 is a medium-severity Missing Authorization vulnerability in the Super Progressive Web Apps WordPress plugin, affecting versions <= 2.2.21. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.2.22; sites on affected versions should update now. Disclosed November 2023, reported by Abdi Pranata.

Vulnerability Overview

The Super Progressive Web Apps plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the superpwa_newsletter_submit() function hooked via a nopriv AJAX action in versions up to, and including, 2.2.21. This makes it possible for unauthenticated attackers to subscribe to the plugin author's newsletter.

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

Super Progressive Web Apps <= 2.2.21 carries this weakness at superpwa_newsletter_submit(), and reaching it takes a caller who can reach the endpoint. 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 Super Progressive Web Apps the fix is 2.2.22: builds <= 2.2.21 are affected, anything from 2.2.22 onward is not.

Remediation

Update to version 2.2.22, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Super Progressive Web Apps 2.2.22 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