Cm Search And ReplaceWordPress extension · Cminds
CVE-2023-28749
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in CreativeMindsSolutions CM On Demand Search And Replace plugin <= 1.3.0 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the CM On Demand Search And Replace WordPress plugin versions 1.3.0 and below allows attackers to trick authenticated administrators into performing unintended search and replace operations on the database through maliciously crafted requests.
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
Cm Search And ReplaceWordPress extension
<= 1.3.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Verify the plugin is installedCheck the WordPress plugins directory at /wp-content/plugins/ for a folder named 'cminds-cm-search-and-replace' or 'cm-search-and-replace', or view the installed plugins list in WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in the plugins directory or appears in the WordPress admin plugin list
-
Identify the installed versionOpen the main plugin PHP file (usually in the plugin folder root) and locate the Version header in the plugin comment block, or check the version column in WordPress admin under Plugins > Installed PluginsAffected if The version number displayed is 1.3.0 or lower
-
Confirm the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify the plugin shows as 'Active' under the plugin name, or query the wp_options table for the active_plugins optionAffected if The plugin status shows as Active or the plugin appears in the active_plugins option in the database
-
Check for admin session exposureVerify that administrator accounts with access to this plugin exist in the WordPress users table (wp_users) and have administrative privileges (wp_usermeta capability level 7 or 8)Affected if There is at least one user with administrator role who could potentially be tricked into visiting a malicious page while logged in
The environment is affected if the Cminds Cm Search And Replace plugin is installed, active, and running version 1.3.0 or below, where an authenticated administrator could be tricked into performing unintended database search and replace operations via CSRF.
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 plugin to a version beyond 1.3.0 if available, or implement anti-CSRF tokens for state-changing actions and configure SameSite cookie attributes.
Fix this in Cm Search And Replace
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28749 — 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-2023-28749 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