Security readout for executives and security teams
Plain-English summary
Awesome Support for WordPress allowed logged-in users as low as subscribers to view draft and password-protected posts. This is a confidentiality issue: it can expose unpublished or restricted site content, but the provided sources do not show code execution, data modification, or service disruption.
Executive priority
Prioritize remediation where WordPress accounts are broadly available or restricted posts contain sensitive business, customer, or operational information. This is not a critical outage risk, but it can create avoidable information exposure.
Technical view
CVE-2024-0596 is a missing authorization check in Awesome Support’s editor_html() function through version 6.1.7. The listed impact is unauthorized viewing of password-protected and draft posts by authenticated users. The weakness maps to CWE-862. CVE-2024-35741 is described as likely duplicate.
Likely exposure
Exposure is limited to WordPress sites using Awesome Support versions up to and including 6.1.7, especially sites allowing subscriber-level accounts or broader user registration. Public-only sites without low-privilege accounts have lower practical exposure.
Exploitation context
The bundle says exploitation requires authenticated access at subscriber level or above. It is not listed in CISA KEV, and the supplied sources do not report active exploitation. Treat exploit status as unconfirmed from the provided evidence.
Researcher notes
The record contains some ambiguity: the narrative requires subscriber-level access, while the CVSS vector in the bundle shows PR:N. Base operational decisions on the described authenticated attack path unless vendor advisories clarify otherwise.
Mitigation direction
- Inventory WordPress sites for Awesome Support version 6.1.7 or older.
- Update Awesome Support according to vendor guidance and verify the fixed version.
- Restrict or remove unnecessary subscriber-level WordPress accounts.
- Review draft and password-protected posts for sensitive information.
- Monitor vendor, CVE, and Wordfence advisories for duplicate CVE clarification.
Validation and detection
- Check installed Awesome Support versions across all WordPress properties.
- Confirm whether public registration or subscriber accounts are enabled.
- Identify sensitive draft or password-protected posts on affected sites.
- After updating, verify low-privilege users cannot view restricted posts.
- Review WordPress logs for unusual authenticated access to non-public content.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-0596 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e4358e2a-b7f6-44b6-a38a-5b27cb15e1cd?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3033134%40awesome-support&new=3033134%40awesome-support&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.