CVE-2024-43973: WordPress Payment forms, Buy now buttons and Invoicing System plugin <= 2.8.11 - Broken Access Control vulnerability
First published: Fri Nov 01 2024(Updated: )
Missing Authorization vulnerability in AyeCode Ltd GetPaid allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GetPaid: from n/a through 2.8.11.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Ayecode Getpaid | <2.8.12 |
Remedy
Update to 2.8.12 or a higher version.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2024-43973?
The severity of CVE-2024-43973 is classified as high due to the potential for unauthorized access to sensitive data.
How do I fix CVE-2024-43973?
To fix CVE-2024-43973, upgrade AyeCode GetPaid to version 2.8.12 or later to ensure proper access control is enforced.
What systems are affected by CVE-2024-43973?
CVE-2024-43973 affects AyeCode GetPaid versions from n/a through 2.8.11.
What details are available about CVE-2024-43973?
CVE-2024-43973 involves a missing authorization vulnerability allowing exploitation due to incorrectly configured access controls.
Can CVE-2024-43973 be exploited remotely?
Yes, CVE-2024-43973 can be exploited remotely if the affected version is publicly accessible.
- agent/remedy
- agent/weakness
- agent/references
- agent/title
- agent/first-publish-date
- agent/type
- agent/description
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/softwarecombine
- agent/severity
- agent/tags
- agent/source
- vendor/ayecode
- canonical/ayecode getpaid