dbcve.org
Wp MeteorWordPress extension

CVE-2023-26543

HIGH · 8.8 CVSS v3.1 Published 2023-11-13
Fix available
A fix is available. Upgrade to after 3.1.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Aleksandr Guidrevitch WP Meteor Website Speed Optimization Addon plugin <= 3.1.4 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WP Meteor plugin versions 3.1.4 and below allows attackers to trick authenticated administrators into performing unintended actions (such as modifying plugin settings) by forcing their browser to send malicious requests.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing operations including form submissions and AJAX requests; verify request referrer/same-origin headers; ensure WordPress nonce verification is applied to all admin actions.

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
Wp MeteorWordPress extension
Affected:<= 3.1.4

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WP Meteor plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'WP Meteor' in the list
    Affected if WP Meteor appears in the installed plugins list (whether active or inactive)
  2. Identify the installed version
    In the plugins list, look for the version number displayed under the plugin name, or check the plugin's main PHP file header in wp-content/plugins/wp-meteor/
    Affected if The version listed is 3.1.4 or any version lower (e.g., 3.1.3, 3.1.2, etc.)
  3. Check if admin actions lack nonce verification
    Examine the plugin's PHP files for form submissions and AJAX handlers - look for the presence of wp_verify_nonce or check_admin_referer calls in functions that modify plugin settings
    Affected if No nonce verification is found in functions handling state-changing operations (saving settings, updating options, etc.)
  4. Identify state-changing endpoints
    Review plugin code for any $_POST, $_GET, or $_REQUEST handling that modifies data, creates updates, or changes plugin configuration
    Affected if The plugin processes request parameters to modify settings without validating request origin or authenticity

If WP Meteor version 3.1.4 or lower is installed AND the plugin processes admin actions without verifying anti-CSRF tokens (nonces) or same-origin headers, the environment is vulnerable to CVE-2023-26543.

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
Upgrade available Upgrade to a release after 3.1.4
Interim mitigation

Implement anti-CSRF tokens (nonces) for all state-changing operations including form submissions and AJAX requests; verify request referrer/same-origin headers; ensure WordPress nonce verification is applied to all admin actions.

Recommended fix Moderate confidence

Update to the latest available version of WP Meteor (version 3.1.5 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WP Meteor in the plugin list
  4. Check the current version number to confirm it is 3.1.4 or earlier
  5. If an update is available, click 'Update Now' to install the latest version
  6. After updating, verify the plugin is running on a version newer than 3.1.4

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

Fix this in Wp Meteor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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