Wordpress Payments Plugin | Getpaid
Approved changes feed: RSS · Atom
cpe:2.3:a:ayecode_ltd:wordpress_payments_plugin_|_getpaid:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Ayecode Ltd (66c62f63-8efd-552a-90e2-90afbb61f861) |
|---|---|
| Product | Wordpress Payments Plugin | Getpaid (29df278b-f8d2-5f99-8908-504a1001cd00) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-24369 |
vulnerable | 2026-06-08 05:30:04.258874 |
GetPaid < 2.3.4 - Authenticated Stored XSS
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.
Published: 2021-06-21T19:18:18.000Z
Updated: 2024-08-03T19:28:23.918Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.