Security readout for executives and security teams
Plain-English summary
CVE-2024-52410 is a critical flaw in the WordPress Referrer Detector plugin. The issue allows unsafe deserialization, which can let an unauthenticated attacker trigger PHP object injection. The supplied sources rate it 9.8 critical because successful exploitation could affect confidentiality, integrity, and availability.
Executive priority
Treat this as urgent for any WordPress environment using Referrer Detector. Prioritize asset discovery first, then remove or remediate affected versions using vendor-backed guidance. Do not assume exposure without confirming plugin presence.
Technical view
The vulnerability is CWE-502, Deserialization of Untrusted Data, in Phoenixheart Referrer Detector package referrer-detector through version 4.2.1.0. The CVSS vector is network-accessible, low complexity, no privileges, and no user interaction, with high impact across confidentiality, integrity, and availability.
Likely exposure
Exposure is likely limited to WordPress sites with the Phoenixheart Referrer Detector plugin installed at version 4.2.1.0 or earlier. The source bundle does not identify other affected products or platforms.
Exploitation context
The provided bundle does not show CISA KEV listing and does not cite active exploitation. Risk remains high because the flaw is unauthenticated, network reachable, and rated CVSS 9.8.
Researcher notes
Evidence is strong for vulnerability class, affected plugin, and CVSS severity. Evidence is incomplete for exploit-in-the-wild, fixed version, and specific mitigation steps. The affected array contains an unclear version value, so rely on the description stating through 4.2.1.0.
Mitigation direction
- Inventory WordPress sites for the Referrer Detector plugin.
- Identify installed plugin versions and flag 4.2.1.0 or earlier.
- Check Phoenixheart, WordPress plugin, or Patchstack guidance for a fixed version.
- Disable or remove affected installs if no trusted fix is available.
- Monitor vendor and CVE records for updated remediation details.
Validation and detection
- Confirm the plugin slug or package name is referrer-detector.
- Record exact installed versions across all WordPress environments.
- Verify any remediation against vendor or Patchstack guidance.
- Review web logs for suspicious requests to affected WordPress sites.
- Recheck CVE and KEV status during remediation tracking.
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-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-52410 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
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:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/referrer-detector/vulnerability/wordpress-referrer-detector-plugin-4-2-1-0-php-object-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.