dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-2902

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The WP Meteor Website Speed Optimization Addon plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'frontend_rewrite' function's 'WPMETEOR[N]WPMETEOR' placeholder content in all versions up to, and including, 3.4.16 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 WP Meteor plugin for WordPress fails to properly sanitize and escape user input in the frontend_rewrite function's placeholder content (WPMETEOR[N]WPMETEOR). This allows unauthenticated attackers to inject malicious JavaScript that persists on affected pages and executes when users view those pages.

MitigationUpdate to plugin version 3.4.17 or later which contains proper input sanitization and output escaping. Until then, consider disabling the plugin or implementing WAF rules to block XSS payloads in the affected parameters.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 WP Meteor plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate WP Meteor, or check the plugin files in wp-content/plugins/ for the wp-meteor folder and read the main plugin file to find the version header
    Affected if WP Meteor plugin is present and active on the site
  2. Check installed plugin version
    Read the version number from the plugin header in the main plugin PHP file (wp-meteor.php) or view the plugin details in WordPress admin Plugins page
    Affected if The version is prior to 3.4.17 (the fixed release)
  3. Inspect page source for WPMETEOR placeholders
    View the HTML source of any public-facing page on the site and search for strings matching the pattern WPMETEOR[number]WPMETEOR (e.g., WPMETEOR1WPMETEOR)
    Affected if Any WPMETEOR placeholders appear in the page HTML source indicating the frontend_rewrite feature is active
  4. Check for injected scripts in placeholders
    Examine the content between WPMETEOR[N]WPMETEOR markers in the page source for suspicious JavaScript tags, event handlers (onload, onerror, onclick), or script URLs
    Affected if The placeholder content contains unsanitized HTML, script tags, or javascript: URIs that were injected by an attacker

The site is affected if WP Meteor plugin versions below 3.4.17 are installed and the frontend_rewrite feature is active, with WPMETEOR placeholders present in page output containing unsanitized user-supplied content.

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 to plugin version 3.4.17 or later which contains proper input sanitization and output escaping. Until then, consider disabling the plugin or implementing WAF rules to block XSS payloads in the affected parameters.

Recommended fix Moderate confidence

Latest available version (after 3.4.16)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the WP Meteor Website Speed Optimization Addon plugin
  4. Check if an update is available and install the latest version
  5. Verify the updated version is above 3.4.16

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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