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

CVE-2026-3718

HIGH · 7.2 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 ManageWP Worker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'MWP-Key-Name' HTTP request header in all versions up to, and including, 4.9.31. This is due to insufficient input sanitization and output escaping of attacker-controlled header values. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator visits the plugin's connection management page with debug parameters.

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

The ManageWP Worker plugin for WordPress versions up to 4.9.31 contain a stored XSS vulnerability via the unauthenticated 'MWP-Key-Name' HTTP header. Attackers can inject arbitrary JavaScript through this header which gets stored and executes when administrators access the plugin's connection management page with debug parameters enabled.

MitigationUpdate the ManageWP Worker plugin to a version newer than 4.9.31 that includes proper input sanitization and output escaping for the MWP-Key-Name header value.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 ManageWP Worker plugin is installed
    Check your WordPress site's plugin directory for the ManageWP Worker plugin, or inspect the /wp-content/plugins/worker directory.
    Affected if The ManageWP Worker plugin is present on the WordPress site.
  2. Check installed plugin version
    View the main plugin file (such as worker/bootstrap.php or worker/readme.txt) to find the version number, or access it via WordPress admin under Plugins > Installed Plugins.
    Affected if The installed version is 4.9.31 or any earlier version.
  3. Determine if debug mode is enabled
    Inspect the plugin configuration files or settings for debug-related parameters. In WordPress, also check wp-config.php for WP_DEBUG or debug-related constants, and look for any MWP debug settings in the plugin options.
    Affected if Debug parameters or debug mode is enabled in the plugin or WordPress configuration.
  4. Inspect stored MWP-Key-Name header values
    Review your database for any stored values associated with the MWP-Key-Name header in the wp_options table or plugin-specific tables. Check for any unexpected or suspicious values in fields related to managed sites or connection keys.
    Affected if A stored value exists for MWP-Key-Name that contains HTML, JavaScript, or unusual characters.

You are affected if the ManageWP Worker plugin is installed at version 4.9.31 or earlier AND debug mode is enabled AND a malicious MWP-Key-Name header value has been stored in your database.

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 ManageWP Worker plugin to a version newer than 4.9.31 that includes proper input sanitization and output escaping for the MWP-Key-Name header value.

Recommended fix Moderate confidence

ManageWP Worker plugin version higher than 4.9.31 (check WordPress plugin repository for latest stable release)

  1. Check your WordPress installation for the ManageWP Worker plugin
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate the ManageWP Worker plugin
  4. Verify the current installed version is 4.9.31 or below
  5. Update the plugin to the latest available version from the WordPress plugin repository
  6. After updating, verify the new version number in the plugins list
  7. Clear any caches if your site uses caching

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

Have this fixed 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 help mitigating

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-2026-3718 — 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-3718 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