dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-2941

HIGH · 8.8 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Linksy Search and Replace plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'linksy_search_and_replace_item_details' function in all versions up to, and including, 1.0.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to update any database table, any value, including the wp_capabilities database field, which allows attackers to change their own role to administrator, which leads to privilege escalation.

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 Linksy Search and Replace plugin for WordPress versions up to 1.0.4 lacks proper capability checks on the 'linksy_search_and_replace_item_details' function, allowing authenticated users with subscriber-level permissions to execute arbitrary database updates including the wp_capabilities field, enabling privilege escalation to administrator.

MitigationUpdate the plugin to version 1.0.5 or later which includes proper capability validation, or remove the plugin if no update is available. If the plugin is required, implement capability checks (e.g., current_user_can('manage_options')) on all AJAX handlers and database modification functions.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm the plugin is installed
    Navigate to WordPress admin dashboard > Plugins and check if 'Linksy Search and Replace' plugin is installed and active
    Affected if The plugin is installed and active with a version up to 1.0.4
  2. Identify the installed version
    In the Plugins list, find 'Linksy Search and Replace' and note the version number displayed under the plugin name
    Affected if Version is 1.0.4 or lower (the vulnerability exists up to version 1.0.4)
  3. Locate the vulnerable function in plugin files
    Access the plugin files via FTP or file manager, typically in wp-content/plugins/linksy-search-and-replace/, and search for the function named 'linksy_search_and_replace_item_details'
    Affected if The function exists and contains database update logic without a capability check (e.g., no current_user_can('manage_options') before the operation)
  4. Verify AJAX handler registration
    Search the plugin files for add_action calls registering 'wp_ajax_linksy_search_and_replace_item_details' or similar AJAX hooks
    Affected if AJAX handlers are registered without privilege checks, allowing subscriber-level users to trigger them
  5. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the list for any users with the Subscriber role
    Affected if At least one Subscriber-level user account exists, which could be exploited for privilege escalation

You are affected if the Linksy Search and Replace plugin is installed at version 1.0.4 or lower and the vulnerable function lacks proper capability validation, allowing any authenticated user to modify database fields including user capabilities.

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

Update the plugin to version 1.0.5 or later which includes proper capability validation, or remove the plugin if no update is available. If the plugin is required, implement capability checks (e.g., current_user_can('manage_options')) on all AJAX handlers and database modification functions.

Recommended fix Moderate confidence

Version after 1.0.4 (check WordPress plugin repository for latest stable release)

  1. 1. Log in to WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Linksy Search and Replace' plugin
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, update the plugin to the latest version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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