CVE-2024-50483
Access Control in Tareqhasan Meetup ≤ 0.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-50483 is a critical-severity Authorization Bypass Through User-Controlled Key (CWE-639) vulnerability in Tareqhasan Meetup. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 18% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-50483 is an Authorization Bypass Through User-Controlled Key vulnerability, tracked as CWE-639, that affects the Meetup WordPress plugin by Tareq Hasan. The flaw impacts all versions from the initial release through 0.1 and carries a CVSS 3.1 score of 9.8, reflecting network-exploitable conditions with no required authentication or user interaction that can result in full confidentiality, integrity, and availability impacts.
An unauthenticated attacker can supply a crafted user-controlled key to bypass authorization checks, enabling privilege escalation within the WordPress instance. Because the plugin exposes this logic over the network without access controls, remote exploitation can grant administrative capabilities or other elevated rights depending on the targeted functionality.
The Patchstack advisory at the referenced URL identifies the broken authentication issue in the Meetup plugin and provides the canonical vulnerability record for remediation tracking.
EPSS values reached a peak of 0.6562 with a current score of 0.5397, indicating a material rise in predicted exploitation likelihood after disclosure that warrants renewed attention from defenders.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44909
Vulnerability Data
Authorization Bypass Through User-Controlled Key vulnerability in Tareq Hasan Meetup meetup allows Privilege Escalation.This issue affects Meetup: from n/a through <= 0.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforcing approved authorizations on every access request structurally stops a user-controlled key from reaching another user's data.
Requiring explicit access-control decisions on each request blocks unauthorized key-driven access.
Least-privilege restrictions limit the scope of data reachable even if a key check is bypassed.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing authorization policy and least privilege directly blocks user-controlled key tampering that bypasses access checks.
Logical access controls prevent unauthorized data access that results from missing authorization checks on object references.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing authorization checks but does not prevent the weakness in production.
Information access restriction explicitly enforces that users may only retrieve data they are authorized to see, directly addressing user-controlled key bypass.
Access control policy directly requires enforcement of authorization rules that prevent unauthorized access via manipulated keys.
Managing access rights includes ensuring users can only access their own records and not bypass authorization by altering identifiers.
Privileged access rights control restricts what data each user may access, mitigating direct object reference attacks.
Secure development lifecycle includes authorization design but does not itself implement runtime access checks.