CVE-2024-13228
Published: 11 March 2025
Summary
CVE-2024-13228 is a medium-severity Exposure of Private Personal Information to an Unauthorized Actor (CWE-359) vulnerability in Themeum Qubely. Its CVSS base score is 4.3 (Medium).
Operationally, ranked in the top 49.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-54158
Vulnerability details
The Qubely – Advanced Gutenberg Blocks plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.13 via the 'qubely_get_content'. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract…
more
sensitive private, pending, scheduled, password-protected, draft, and trashed post data.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Automated marking identifies private personal information in outputs, tangibly reducing the ability to exploit weaknesses that result in its unauthorized exposure.
Privacy-specific attributes and their controlled association directly reduce exposure of private personal information through missing or incorrect labeling.
Preventing nonpublic personal information from public posting reduces unauthorized exposure of private personal data.
The control detects and protects against mining of private personal information, reducing unauthorized exposure of PII.
Privacy literacy training directly targets preventing exposure of personal information through user mishandling.
Tracking locations of sensitive data and access users reduces risk of private personal information exposure.
PIA explicitly identifies PII collection/use/disclosure flows and drives mitigations that reduce the likelihood of unauthorized exposure of private personal information.
The control specifically requires architectures that minimize privacy risk when processing PII, directly addressing exposure of personal information.