dbcve.org
Word Replacer ProWordPress extension · Charlestsmith

CVE-2024-1733

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The Word Replacer Pro plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the word_replacer_ultra() function in all versions up to, and including, 1.0. This makes it possible for unauthenticated attackers to update arbitrary content on the affected WordPress site.

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 confidence

The Word Replacer Pro plugin for WordPress lacks a capability check on the word_replacer_ultra() function, allowing unauthenticated attackers to modify arbitrary content on the site. This is a broken access control vulnerability where an AJAX or other callable function does not verify user permissions before executing.

MitigationAdd a WordPress capability check (e.g., current_user_can('manage_options')) at the beginning of the word_replacer_ultra() function to ensure only authorized administrators can modify content. Update to the latest plugin version if a patched release is available.

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
Word Replacer ProWordPress extension
Affected:= 1.0

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 Word Replacer Pro plugin is installed
    Check your WordPress installation for the Word Replacer Pro plugin (by Charlestsmith) in the wp-content/plugins directory or via WordPress admin plugin list
    Affected if The plugin is installed and active
  2. Confirm the installed version is 1.0
    Check the plugin header in the main plugin file (typically word-replacer-pro.php or similar) for the Version field, or view the plugin details in WordPress admin under Plugins
    Affected if Version is 1.0 (the only affected version listed)
  3. Locate the word_replacer_ultra() function
    Search the plugin source files for the function named word_replacer_ultra() - typically found in the main plugin PHP file or an includes/AJAX handler file
    Affected if The function exists in the plugin code
  4. Inspect the function for capability checks
    Examine the word_replacer_ultra() function body to see if it includes a permission check such as current_user_can() or similar WordPress capability verification before executing
    Affected if No capability check (e.g., current_user_can) is present before the function logic executes
  5. Verify AJAX or callable endpoints are accessible without authentication
    Check the add_action() calls registering the function to AJAX hooks (wp_ajax_ or wp_ajax_nopriv_) and determine if the function can be triggered by unauthenticated users
    Affected if The function is registered to an AJAX hook accessible to unauthenticated users (hooks like wp_ajax_nopriv_ or direct call without auth)

You are affected if Word Replacer Pro version 1.0 is installed, the word_replacer_ultra() function lacks a capability check, and the function is callable by unauthenticated users via AJAX or other endpoints.

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

Add a WordPress capability check (e.g., current_user_can('manage_options')) at the beginning of the word_replacer_ultra() function to ensure only authorized administrators can modify content. Update to the latest plugin version if a patched release is available.

Fix this in Word Replacer Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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