CVE-2021-36844

WP Subscribe <= 1.2.12 - Authenticated (Admin+) Stored Cross-Site Scripting

2022-05-02 14:11
Asif Nawaz Minhas

Strategic Overview

Status
Patched in 1.2.13
Affected Plugin
WP Subscribe
Affected Version
<= 1.2.12
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-36844
View all WP Subscribe vulnerabilities

At a glance

CVE-2021-36844 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Subscribe WordPress plugin, affecting versions <= 1.2.12. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.2.13; sites on affected versions should update now. Disclosed May 2022, reported by Asif Nawaz Minhas.

Vulnerability Overview

WP Subscribe versions up to 1.2.12 is vulnerable to Cross-Site Scripting. This allows authenticated attackers to inject JavaScript into the database.

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

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WP Subscribe <= 1.2.12 takes an account at Admin level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP Subscribe the fix is 1.2.13: builds <= 1.2.12 are affected, anything from 1.2.13 onward is not.

Remediation

Update to version 1.2.13, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Subscribe 1.2.13 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