CVE-2024-52410
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDeserialization of Untrusted Data vulnerability in Phoenixheart Referrer Detector referrer-detector allows Object Injection.This issue affects Referrer Detector: from n/a through <= 4.2.1.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a PHP Object Injection vulnerability in the Phoenixheart Referrer Detector library. The application deserializes untrusted data (likely from user input such as HTTP headers) without proper validation, allowing attackers to inject malicious serialized PHP objects that can lead to remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Phoenixheart Referrer Detector library in your codebaseSearch your vendor directory, composer.json, or project dependencies for 'phoenixheart' or 'referrer-detector' to find the library filesAffected if The library is present and included in your project dependencies
-
Identify the installed version of the libraryCheck the composer.lock file or the library's composer.json for the version number, then compare it against any known affected versionsAffected if The version is at risk based on version comparison (no specific safe version listed; assume all versions may be affected if they use unserialize())
-
Find code that calls unserialize() without allowed_classesSearch the library source code for 'unserialize(' calls and inspect whether the second parameter (allowed_classes) is set to a whitelist or is missing entirelyAffected if unserialize() is called without a strict allowed_classes whitelist parameter
-
Identify if HTTP headers or user input reach the deserializationTrace the data flow from HTTP request headers (such as Referer, User-Agent, or custom headers) to the unserialize() call in the libraryAffected if Untrusted HTTP headers or user-controlled input are passed directly to unserialize() without validation
-
Verify if input validation or sanitization exists before deserializationSearch for input validation functions (filter_var, preg_match, etc.) or sanitization logic that occurs before the unserialize() callAffected if No validation or sanitization is performed on the data before it is deserialized
Your environment is affected if the Phoenixheart Referrer Detector library is installed and its code uses unserialize() on untrusted input from HTTP headers or other user data without implementing a strict allowed_classes whitelist or input validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace unsafe PHP unserialize() calls with json_decode() or implement a strict allowed_classes whitelist if serialization must be used. Validate and sanitize all input before deserialization.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52410 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data