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

CVE-2026-2277

MEDIUM · 6.1 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 →
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 rexCrawler plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'url' and 'regex' parameters in the search-pattern tester page in all versions up to, and including, 1.0.15 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick an administrator into performing an action such as clicking on a link. This only affects multi-site installations and installations where unfiltered_html has been disabled.

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 rexCrawler WordPress plugin versions up to 1.0.15 contain a reflected XSS vulnerability in the search-pattern tester page. The 'url' and 'regex' parameters lack proper input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary JavaScript via crafted links that trick administrators into clicking them.

MitigationUpdate the rexCrawler plugin to a version beyond 1.0.15 when available, or disable the plugin until a patch is released. For multi-site installations or sites with unfiltered_html disabled, this should be treated as high priority.

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. Confirm rexCrawler plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'rexCrawler' in the list of active or inactive plugins.
    Affected if The plugin does not appear in the plugin list.
  2. Identify installed rexCrawler version
    In the WordPress plugins list, locate the rexCrawler plugin entry and note the version number displayed below the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/rexcrawler/rexcrawler.php for the 'Version' tag.
    Affected if The installed version is 1.0.15 or any version up to 1.0.15.
  3. Verify search-pattern tester functionality is accessible
    Check if the plugin exposes a tester page by visiting common paths such as /wp-admin/admin.php?page=rexCrawler or /?page=rexCrawler, or by reviewing the plugin menu items in the WordPress admin sidebar.
    Affected if The search-pattern tester page or associated menu item exists and is accessible.
  4. Inspect URL parameter handling for XSS vectors
    Access the search-pattern tester page and test the 'url' and 'regex' parameters by submitting values containing script tags or event handlers (for example, url parameter with 'javascript:alert(1)'). Observe whether the input is reflected back without encoding in the page response.
    Affected if The submitted values are reflected in the response without proper HTML encoding or sanitization.

If rexCrawler is installed with version 1.0.15 or lower and the search-pattern tester page is accessible, the environment is affected by this reflected XSS vulnerability.

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 rexCrawler plugin to a version beyond 1.0.15 when available, or disable the plugin until a patch is released. For multi-site installations or sites with unfiltered_html disabled, this should be treated as high priority.

Recommended fix High confidence

rexCrawler version 1.0.16 or later

  1. Backup your WordPress site before proceeding
  2. Update the rexCrawler plugin to the latest available version from the WordPress plugin repository
  3. After updating, verify the plugin is functioning correctly
  4. Clear any site caches if you use caching plugins
  5. Confirm the vulnerability is resolved by testing the 'url' and 'regex' parameters in the search-pattern tester page

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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