Security readout for executives and security teams
Plain-English summary
Majestic Support for WordPress could store support ticket attachments in a web-accessible uploads directory. On affected sites, an unauthenticated visitor may be able to retrieve sensitive files from support tickets. The primary business risk is confidentiality loss, not site takeover or service outage.
Executive priority
Treat this as a high-priority confidentiality incident risk for any customer-facing WordPress support portal. Prioritize sites handling identity documents, contracts, invoices, credentials, or regulated support data. Response urgency depends on whether exposed attachments exist and whether logs show access.
Technical view
CVE-2024-13600 is a CWE-200 sensitive information exposure in Majestic Support versions up to and including 1.0.5. The exposed path is /wp-content/uploads/majesticsupportdata, which may contain support ticket attachments. CVSS 3.1 is 7.5: network-accessible, low complexity, no privileges, no user interaction, high confidentiality impact.
Likely exposure
Exposure is most likely on public WordPress sites running Majestic Support 1.0.5 or earlier, especially where customers or staff attached files to support tickets. Sites without this plugin, without ticket attachments, or with effective server-side access controls are less exposed.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The issue is still easy to abuse if the directory is reachable, because the stated attack path requires no authentication or user interaction.
Researcher notes
The bundle names the vulnerable directory and affected versions but does not provide exploit telemetry or a fixed version number. Avoid assuming compromise from plugin presence alone; validate installed version, directory reachability, attachment contents, and historical access logs.
Mitigation direction
- Identify all WordPress sites running Majestic Support.
- Review Wordfence and vendor guidance for the fixed release.
- Update from versions 1.0.5 and earlier as soon as possible.
- Restrict public access to the majesticsupportdata uploads directory.
- Remove or relocate sensitive ticket attachments if exposure occurred.
- Review whether affected support tickets contained regulated data.
Validation and detection
- Inventory Majestic Support versions across managed WordPress sites.
- Confirm whether /wp-content/uploads/majesticsupportdata is publicly reachable.
- Review web logs for unauthenticated access to that directory.
- Sample stored ticket attachments for sensitive business or customer data.
- Verify the plugin is updated beyond affected versions.
- Confirm directory access controls remain effective after update.
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-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCVE-2024-13600 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c5a8fd90-49dd-4a5e-88f2-cd6b338da2d6?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.0.5/includes/classes/uploads.phpCVE reference
- https://plugins.trac.wordpress.org/changeset/3231938/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.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.