CVE-2021-24313 json
WP Prayer < 1.6.2 - Authenticated Stored Cross-Site Scripting (XSS)
published 5y ago modified 4mo ago also EUVD-2021-11227
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- goprayer wp_prayer 1.6.2
Is CVE-2021-24313 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/c7ab736d-27c4-4ec5-9681-a3f0dda86586 referenced PoC, tagged "exploit" by a source, unverified
- bastijnouwendijk.com https://bastijnouwendijk.com/cve-2021-24313/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Affected products
- Unknown WP Prayer
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wpscan.com
/vulnerability/c7ab736d-27c4-4ec5-9681-a3f0dda86586
exploit, third-party-advisory
-
bastijnouwendijk.com
/cve-2021-24313/
exploit, technical-description, third-party-advisory
Sources
- CVE List CVE-2021-24313
- NVD CVE-2021-24313
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.