WP Prayer <= 1.6.1 - Authenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.6.2
- Affected Plugin
- WP Prayer
- Affected Version
< 1.6.2- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24313
At a glance
CVE-2021-24313 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Prayer WordPress plugin, affecting versions < 1.6.2. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 1.6.2; sites on affected versions should update now. Disclosed May 2021, reported by Bastijn Ouwendijk.
Vulnerability Overview
The WP Prayer WordPress plugin before 1.6.2 provides the functionality to store requested prayers/praises and list them on a WordPress website. These stored prayer/praise requests can be listed by using the WP Prayer engine. An authenticated WordPress user with any role can fill in the form to request a prayer. The form to request prayers or praises have several fields. The 'prayer request' and 'praise request' fields do not use proper input validation and can be used to store XSS payloads.
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')
WP Prayer < 1.6.2 carries this weakness at and, and reaching it 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 WP Prayer the fix is 1.6.2: builds < 1.6.2 are affected, anything from 1.6.2 onward is not.
Remediation
Update to version 1.6.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Prayer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Prayer 1.6.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP Prayer
- 4.3CVE-2024-3407: WP Prayer <= 2.0.9 CSRF to Arbitrary Prayer Deletion
CVE-2024-3407 - 4.3CVE-2024-3406: WP Prayer <= 2.0.9 CSRF to Email Settings Update
CVE-2024-3406 - 4.3CVE-2024-3405: WP Prayer <= 2.0.9 CSRF to Settings Update
CVE-2024-3405 - 4.3WP Prayer <= 1.5.4 Cross-Site Request Forgery
- 4.3CVE-2021-4412: WP Prayer <= 1.6.5 Cross-Site Request Forgery Bypass
CVE-2021-4412
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C