CVE-2024-44052: WordPress HelloAsso plugin <= 1.1.10 - Broken Access Control vulnerability
First published: Fri Nov 01 2024(Updated: )
Missing Authorization vulnerability in HelloAsso allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects HelloAsso: from n/a through 1.1.10.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| HelloAsso | <1.1.11 |
Remedy
Update to 1.1.11 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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-44052?
CVE-2024-44052 has a medium severity rating due to the risk of unauthorized access exploitation.
How do I fix CVE-2024-44052?
To fix CVE-2024-44052, update HelloAsso to version 1.1.11 or later to rectify the access control configuration.
What types of systems are affected by CVE-2024-44052?
CVE-2024-44052 affects HelloAsso versions prior to 1.1.11 on WordPress installations.
What is the impact of CVE-2024-44052?
The impact of CVE-2024-44052 includes potential unauthorized access to sensitive areas of HelloAsso.
Is there a workaround for CVE-2024-44052?
Currently, the recommended approach is to update the plugin, as there are no effective workarounds to mitigate the issue.
- agent/weakness
- agent/references
- agent/title
- agent/remedy
- agent/type
- agent/first-publish-date
- agent/description
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/softwarecombine
- agent/severity
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/helloasso
- canonical/helloasso