CVE-2021-24369 GetPaid < 2.3.4 - Authenticated Stored XSS
Authenticated users can inject malicious scripts via unsanitized input fields in the GetPaid plugin, potentially leading to privilege escalation when admins view the forms.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2021-24369?
CVE-2021-24369 is a medium-severity cross-site scripting vulnerability in AyeCode Ltd WordPress Payments Plugin | GetPaid, published on 21 Jun 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-79
Which versions are affected by CVE-2021-24369?
It affects 1 product.
Products include Ayecode Getpaid.
How do I fix CVE-2021-24369?
No fix has been published for CVE-2021-24369 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2021-24369 being exploited?
There is no known exploitation of CVE-2021-24369 in the wild and no public exploit code.
Other vulnerabilities in AyeCode Ltd WordPress Payments Plugin | GetPaid
Sources
Also known as GHSA-83pg-f5q7-v37g.