dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-49227

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-16
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 foter Free Stock Photos Foter free-stock-photos-foter allows Object Injection.This issue affects Free Stock Photos Foter: from n/a through <= 1.5.4.

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

A deserialization of untrusted data vulnerability in the Free Stock Photos Foter WordPress plugin (versions <= 1.5.4) allows attackers to inject malicious PHP objects, potentially leading to remote code execution via PHP object injection attacks.

MitigationUpgrade to a patched version of the Foter plugin that properly validates or sanitizes deserialized data, or replace unsafe unserialize() calls with safer alternatives like json_decode.

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. Verify Foter plugin is installed
    Check the WordPress plugins directory for the Foter plugin folder, typically located in wp-content/plugins/. List installed plugins via wp-cli: wp plugin list --status=active --field=name, or inspect the plugins list in the WordPress admin dashboard.
    Affected if The Foter plugin appears in the list of installed or active plugins.
  2. Identify installed Foter plugin version
    Open the main plugin file (usually named foter.php or similar in the plugin folder) and locate the plugin header comment which contains the Version field. Alternatively, check the WordPress plugin repository page for the installed version, or use wp-cli: wp plugin get foter --field=version.
    Affected if The reported version is 1.5.4 or lower.
  3. Locate vulnerable unserialize() calls
    Search the plugin source code for calls to unserialize() function. Use grep or a file search to scan PHP files in the plugin directory for the pattern: unserialize( . Review any unserialize() calls that process input from $_GET, $_POST, $_REQUEST, or other user-supplied data sources.
    Affected if The plugin code contains unserialize() calls that process untrusted input without prior sanitization or validation.
  4. Verify user input reaches unserialize()
    Trace the data flow from HTTP request parameters to the unserialize() call. Identify which plugin files, functions, or endpoints accept and process serialized data. Check if the affected code is reachable via publicly accessible URLs or admin AJAX actions.
    Affected if User-controlled data from request parameters flows directly into an unserialize() call without validation.

You are affected if the Foter WordPress plugin is installed at version 1.5.4 or lower AND the plugin code contains unserialize() calls that process untrusted input from HTTP requests.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of the Foter plugin that properly validates or sanitizes deserialized data, or replace unsafe unserialize() calls with safer alternatives like json_decode.

Recommended fix Moderate confidence

Update to the latest available version of Free Stock Photos Foter plugin (check WordPress plugin repository for the current version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Free Stock Photos Foter' plugin (free-stock-photos-foter)
  4. If an update is available, click 'Update Now' to install the latest version
  5. After updating, verify the plugin is running on a version newer than 1.5.4
  6. Test that the plugin functionality works as expected in the frontend

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49227 — 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-49227 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