WordPress Payments Plugin | GetPaid <= 2.3.3 - Authenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.3.4
- Affected Version
<= 2.3.3- CVSS
- 5.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24369
At a glance
CVE-2021-24369 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Payment forms, Buy now buttons, and Invoicing System WordPress plugin, affecting versions <= 2.3.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.3.4; sites on affected versions should update now. Disclosed June 2021, reported by Jorgson.
Vulnerability Overview
In the GetPaid WordPress plugin before 2.3.4, users with the contributor role and above can create a new Payment Form, however the Label and Help Text input fields were not getting sanitized properly. So it was possible to inject malicious content such as img tags, leading to a Stored Cross-Site Scripting issue which is triggered when the form will be edited, for example when an admin reviews it and could lead to privilege escalation.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Payment forms, Buy now buttons, and Invoicing System <= 2.3.3 takes any authenticated account. 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 Payment forms, Buy now buttons, and Invoicing System the fix is 2.3.4: builds <= 2.3.3 are affected, anything from 2.3.4 onward is not.
Remediation
Update to version 2.3.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Payment forms, Buy now buttons, and Invoicing System: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Payment forms, Buy now buttons, and Invoicing System 2.3.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Payment forms, Buy now buttons, and Invoicing System | GetPaid
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C