dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-49318

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Deserialization of Untrusted Data vulnerability in Scott My Reading Library my-reading-library allows Object Injection.This issue affects My Reading Library: from n/a through <= 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 · moderate confidence

The My Reading Library application contains a PHP Object Injection vulnerability where unserialize() is called on untrusted user-controlled data, potentially allowing remote code execution through the instantiation of malicious objects with magic methods like __wakeup() or __destruct().

MitigationReplace all unserialize() calls with json_decode() or another safe deserialization method, and implement proper input validation and authentication on data entry points.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of My Reading Library
    Check the application source code for a version file, or look in configuration files, composer.json, or a README for a version number. Common locations include: /version.php, /config.php, composer.json 'version' field, or a changelog file.
    Affected if The installed version cannot be determined or is unknown/unpatched.
  2. Locate unserialize() calls in the application code
    Search the codebase for 'unserialize(' using grep or a similar tool. Example: grep -r "unserialize(" /path/to/application/ --include="*.php"
    Affected if Any unserialize() call exists in PHP files within the application directory.
  3. Determine if user input reaches unserialize()
    Analyze the code paths from where unserialize() is called backwards to identify if $_GET, $_POST, $_COOKIE, or other user-supplied data flows to it. Check the function/class containing unserialize() to see its input sources.
    Affected if User-controlled data (from request parameters, cookies, or headers) is passed directly to unserialize() without sanitization.
  4. Verify if authentication is required to reach the vulnerable code
    Review the code around the unserialize() call to determine if it is within a function or file that executes after a login check, session validation, or other access control.
    Affected if The vulnerable unserialize() call is reachable without any authentication or authorization check.
  5. Identify magic method classes that could be exploited
    Search for PHP class definitions containing __wakeup(), __destruct(), __toString(), or __get() magic methods in the application or included libraries. Example: grep -r "function __wakeup" --include="*.php"
    Affected if Magic method classes exist in the application and are autoloadable, making RCE possible if unserialize() is exploitable.
  6. Check PHP configuration for deserialization restrictions
    Review php.ini for the unserialize() options. The setting 'unserialize_callback_func' specifies a callback, and 'allow_url_fopen'/'allow_url_include' affect related attacks. Check: ini_get('unserialize_callback_func')
    Affected if PHP configuration does not block or warn on dangerous unserialize() operations.

A user is affected if the My Reading Library application contains any unserialize() call that processes untrusted user input without prior validation, and that code path is reachable in the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace all unserialize() calls with json_decode() or another safe deserialization method, and implement proper input validation and authentication on data entry points.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49318 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-49318 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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