WP-Recall <= 16.24.47 - Reflected Cross-Site Scripting

2021-10-05 00:00
WPScanTeam

Strategic Overview

Status
Patched in 16.24.48
Affected Plugin
WP-Recall – Registration, Profile, Commerce & More
Affected Version
<= 16.24.47
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all WP-Recall – Registration, Profile, Commerce & More vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP-Recall WordPress plugin, affecting versions <= 16.24.47. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 16.24.48; sites on affected versions should update now. Disclosed October 2021, reported by WPScanTeam.

Vulnerability Overview

The WP-Recall plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'date-start' and 'end-start' parameters in versions up to, and including, 16.24.47 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user 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.

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

WP-Recall <= 16.24.47 carries this weakness at date-start, and reaching it takes a caller who can reach the endpoint. 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-Recall the fix is 16.24.48: builds <= 16.24.47 are affected, anything from 16.24.48 onward is not.

Remediation

Update to version 16.24.48, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/ccd2ef23-23b7-4a32-aeda-41ea9439f166

Related records

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