# 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.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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 available:** No
- **Published:** 21 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-83pg-f5q7-v37g

## 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 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2021-24369?

It affects 1 product.


Products: 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.

## 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

- [CVE-2024-43973](https://insights.sbomify.com/CVE-2024-43973/): WordPress GetPaid plugin <= 2.8.11 - Broken Access Control vulnerability (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24369 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2021-24369 in the wild and no public exploit code.

Affected product: AyeCode Ltd WordPress Payments Plugin | GetPaid. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-24369/ (Markdown: https://insights.sbomify.com/CVE-2021-24369/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-24369
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-24369
- OSV: https://osv.dev/vulnerability/CVE-2021-24369

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-24369/
Summaries are generated and may contain mistakes; the official description above is the record.