XSS in Ayecode Getpaid
CVE-2021-24369
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.
Vulnerability class: XSS (Cross-Site Scripting)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N.
EPSS exploit prediction
EPSS: 0.006 (50.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 50th percentile — 50.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.006 · newest: 0.006 · change: 0.000
Affected products
- Ayecode Getpaid
- Ayecode Ltd WordPress Payments Plugin | Getpaid — versions 2.3.4
Weakness classification (CWE)
Public proof-of-concept exploits
References
- wpscan.com/vulnerability/1d1a731b-78f7-4d97-b40d-80f66700edae (Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2021-24369?
- CVE-2021-24369 is a medium-severity vulnerability in Ayecode Getpaid, classified under Cross-site Scripting. CVSS score: 5.4/10. Published 2021-06-21.
- How severe is CVE-2021-24369?
- Medium severity. CVSS v3 base score is 5.4 out of 10.
- Is CVE-2021-24369 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.