Approved changes feed: RSS · Atom
cpe:2.3:a:ayecode:getpaid:*:*:*:*:*:wordpress:*:*
part: a version: * update: *
| Vendor | Ayecode (075372bf-4710-5b02-aa7e-ef70a5044052) |
|---|---|
| Product | Getpaid (77fe6027-e44e-5876-b322-80de68147cef) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | wordpress |
| 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-2024-43973 |
vulnerable | 2026-06-03 14:56:47.159510 |
WordPress GetPaid plugin <= 2.8.11 - Broken Access Control vulnerability
MEDIUM (4.3)
Missing Authorization vulnerability in Stiofan GetPaid invoicing allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GetPaid: from n/a through <= 2.8.11.
Published: 2024-11-01T14:17:14.989Z
Updated: 2026-04-28T16:10:14.767Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-24369 |
vulnerable | 2026-06-03 14:43:56.932418 |
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.