Donate With QRCode <= 1.4.4 - Authenticated (Subscriber+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.4.5
- Affected Plugin
- 博客社交分享组件
- Affected Version
<= 1.4.4- CVSS
- 5.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24618
At a glance
CVE-2021-24618 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the 博客社交分享组件 WordPress plugin, affecting versions <= 1.4.4. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.4.5; sites on affected versions should update now. Disclosed August 2021, reported by yangshengcheng@webray.com.cn inc.
Vulnerability Overview
The Donate With QRCode WordPress plugin before 1.4.5 does not sanitise or escape its QRCode Image setting, which result into a Stored Cross-Site Scripting (XSS). Furthermore, the plugin also does not have any CSRF and capability checks in place when saving such setting, allowing any authenticated user (as low as subscriber), or unauthenticated user via a CSRF vector to update them and perform such attack.
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 博客社交分享组件 <= 1.4.4 takes an account at Subscriber 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 博客社交分享组件 the fix is 1.4.5: builds <= 1.4.4 are affected, anything from 1.4.5 onward is not.
Remediation
Update to version 1.4.5, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber 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: 博客社交分享组件 1.4.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in 博客社交分享组件
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C