Search \& ReplaceWordPress extension · Wp Media
CVE-2024-38759
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 WP MEDIA SAS Search & Replace search-and-replace.This issue affects Search & Replace: from n/a through 3.2.2.
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 confidenceA deserialization vulnerability in the WP MEDIA SAS Search & Replace WordPress plugin (versions through 3.2.2) allows unauthenticated attackers to deserialize untrusted data, potentially leading to remote code execution. The Search & Replace plugin handles database content manipulation, and improper handling of serialized data inputs enables attackers to inject malicious objects. With a CVSS score of 9.8 (Critical) and network-exploitable with no authentication required, this vulnerability poses severe risk to WordPress installations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Search \& ReplaceWordPress extension
<= 3.2.2CVSS 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 Search & Replace plugin installationInspect the WordPress plugins directory (typically /wp-content/plugins/) for a folder named 'search-and-replace', 'search-replace', or similar variation containing 'search' and 'replace' in the name.Affected if The plugin folder exists in the plugins directory.
-
Identify the installed plugin versionOpen the main plugin file (usually named search-and-replace.php or similar) and locate the version header in the plugin comment block. Alternatively, check the readme.txt file in the plugin folder for the 'Stable tag' or 'Version' entry.Affected if The version displayed is 3.2.2 or any version lower than 3.2.2.
-
Confirm plugin is active on the WordPress siteLog in to the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate the Search & Replace plugin in the list and verify its status. Alternatively, query the wp_options table in the database for the option_name 'active_plugins' to check if the plugin is included.Affected if The plugin shows as 'Active' or is present in the active_plugins array.
-
Check for exposed deserialization endpointsReview the plugin's AJAX handlers or direct PHP files accessible via web requests. Look for PHP functions that handle unserialize() on user-controlled input, typically found in ajax or admin-post PHP files within the plugin folder.Affected if The plugin handles serialized data from unauthenticated requests.
If the Search & Replace plugin is installed, active, and running version 3.2.2 or lower, the site is vulnerable to unauthenticated deserialization attacks.
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 dataUpdate the Search & Replace plugin to the latest patched version immediately. If no patched version is available, disable the plugin and consider removing it until a fix is released.
Fix this in Search \& Replace
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38759 — 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-38759 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